Sandbox Settings-> Applications -> Web Browser -> Firefox -> Allow direct access to Firefox bookmark and history database). The good news is the spike should be temporary, the bad news is we'll probably get a bit of a rough ride into release as well.Version history for Sandboxie (32-bit & 64-bit) This would probably have caused other seemingly spurious (and temporary) issues/crashes in the past. So, this really seems to indicate some problems with the update process that means we can get a mismatch between firefox.exe and xul.dll. I tried out this theory, by installing Fx53b8 and copying in the xul.dll from Fx53b9 and hey presto, it produces the exact same crash: This also explains why it is reported on the wrong/old versions. What I think is happening is during the update, in some circumstances we end up with an old firefox.exe running with a new xul.dll (or possibly vice versa). We use the broker services to create the sandbox::TargetPolicy (mPolicy) that is blowing up on us. Now the sandbox code is linked into firefox.exe not xul.dll and we pass pointers to the sandbox::BrokerServices from firefox.exe through to xul.dll. Now the two things these changesets have in common (aside from the fact they are mine :-) ), is that they contain updates to the chromium sandbox code. I realised the first spike couldn't have been bug 1344453 as that hadn't landed at all, so that must have been bug 1337331.
0 kommentar(er)
