Hi Tzuk,

I have been using the betas, including the latest version and have been getting random freezes in Opera 10.10 build 1893 (javascript, plugins, java, disabled) running within Windows 7 64. The freezes are sporadic and sometimes occur when trying to initiate a download or sometimes when just selecting a link on a page. Opera cpu usage spikes.

To eliminate the freeze, I can right-click on the sandboxie control icon in the system tray. As soon is this is done everything returns to normal. I am running no other security software; I do have Admuncher 4.81 b31325. Also, I have no problems running Firefox sandboxed.

Thanks for the new version.

Michael

I take it that no one else is having this problem. Unfortunately, I continue to experience these random freezes w/ beta 3.43.18_64. I have tried to eliminate other causes by disabling Ad Muncher, creating a new sandbox, and installing the latest Opera beta, but with no luck.

I can reproduce the same effect frequently, which normally occurs randomly, if I quickly click a link repeatedly, such as a, Sandboxie forum topic, which normally one would only click once. The freeze will occur at this point. Hope that makes some sense.

If it can't be reproduced I won't mention it again. Thanks.

I've been unable to reproduce the freezes running Opera 10.10 build 1893 with any of the 64-bit betas. Enabling or disabling my web proxy (Proxomitron) makes no difference.

I would suggest using WinDbg. Follow the instructions here: How To Use Win Dbg. Use Scenario 2 and attach WinDbg to the Opera process while it's frozen. You can get the 64-bit version of Debugging Tools for Windows here: Download Debugging Tools for Windows - Native x64.

I've just addressed an issue with programs freezing:

http://www.sandboxie.com/phpbb/viewtopic.php?t=7128

Perhaps that will also resolve the problem with Opera. Please try version 3.43.19 when I release it. I'd rather you do the debugger thing with version 3.43.19 anyway.

Thanks Nick & Tzuk for the feedback. I tried 3.43.19 and still had the same problem. I could manually recreate it in the manner I previously described. I am including the Windbg log, however, I am not positive that I did it correctly.


snipped. --tzuk

Looks like you followed the steps correctly, but unfortunately due to Wow64, we cannot get a useful stack trace. Your log shows what the 64-bit parts in Opera.exe are doing, and with Opera being a 32-bit program, clearly the interesting parts are 32-bit. I don't know how you can tell the 64-bit debugger that you want to see the 32-bit parts of a running program. Perhaps you can try this again with the 32-bit debugger? Although I can't be sure that it will make a difference.

I went ahead and installed the 32 bit debugger.

snipped. --tzuk

I think that it's possible with remote debugging.

Thanks Michael, this is the log I was expecting to see the first time, so it looks like the 32-bit debugger is in fact better at looking at 32-bit programs, than the 64-bit debugger.

From this log, I'm afraid I don't see how Sandboxie code plays a part in the problem. However I see that in both logs, some time after you enter the g command, the following lines appear:

0:013> g
(c9c.d1c): Unknown exception - code 000006ba (first chance)
(c9c.d1c): Unknown exception - code 000006ba (first chance)
(c9c.d1c): Unknown exception - code 000006ba (first chance)

So what I want you to do is start the Resource Access Monitor in Sandboxie just before you enter "g", and close the Resource Access Monitor after you see these three "Unknown exception" messages appear in the debugger.

Thanks.

Thanks Tzuk, with your latest advice I was able to solve the problem!

The resource monitor listed Objectdock as one of the first entries. Since I had been using Sandboxie for years, prior to moving to Windows 7 64, I added my old saved sandboxie.ini. However, in my old settings I remembered I had removed the Objectdock exclusion because I never came across a need for it. After enabling the exclusion, everything works great. Not sure why it seems to only effect Opera, but I am glad it's solved.

Thanks for the wonderful support as always and hope that the new 64-bit version proves successful for you.

Michael

Care to post the exclusions you added? Maybe tzuk will want to add them to Sandboxie's internal default list.

Sorry wraithdu, I meant I added the internal default exclusion for Objectdock. I previously removed it under Vista 32 and never experienced the same problem so I overlooked it as a cause.