![]() |
| the following plug-in is unresponsive: Shockwave Flash |
|
SnDPhoenix
|
Yeah, I've been getting this message ALOT myself, but only with Chrome/Chromium in Sandboxie!
I always install Chrome (or nightly Chromium builds) sandboxed as opposed to installing Chrome unsandboxed and running it sandboxed, so that might have something to do with it, but sometimes I can load pages with flash objects and never see that error message! It should be noted however, that in my case Flash always runs fine, contrary to the popup message stating that Flash is "Unresponsive", so I always just click 'No' at the prompt and continue whatever I was doing. |
||||||||||||
|
|
|||||||||||||
|
tzuk
|
While working on version 3.52, I fixed a few issues with Chrome and Flash but I did not see this pop up message. Is there some way that I can consistently reproduce the problem or is it seemingly random?
|
||||||||||||
|
_________________ tzuk |
|||||||||||||
|
SnDPhoenix
|
Yeah it's pretty random in my case.
The only (sort of) consistent way I can think of reproducing it, is to install the latest Dev build of Chrome sandboxed, then try playing some Youtube videos and see if you get the "Unresponsive" popup at some point, in my case this usually works about 95% of the time. |
||||||||||||
|
|
|||||||||||||
|
tzuk
|
Well, if I'm going to be shooting in the dark trying to reproduce this, I might as well try on the right kind of system . . . So Windows 7, but 32-bit or 64-bit?
|
||||||||||||
|
|
|||||||||||||
|
SnDPhoenix
|
In my case, Windows 7 32-bit
|
||||||||||||
|
|
|||||||||||||
|
uker
|
Thanks for the quick response. I've got the 32 bit, too. My problem is 100% consistent - and is that way in firefox or IE as well: Youtube works great in all 3 by themselves, but will not work while using them sandboxed. The fact that the sandboxed Chrome asks me if I want to make it default (it is already set as default on my system) makes me think that it isn't reading all the settings on my computer like it use to. My gut tells me that something may have changed in the default settings over the last few builds that created this problem (I've had it for a couple of months now). I'm just not seeing the setting that needs changed.
Also, I use sandboxie at work (running Chrome or Firefox in XP) and have not had these problems. |
||||||||||||
|
|
|||||||||||||
|
SnDPhoenix
|
Hmm, interesting... You and I both receive these "Unresponsive..." pop-ups on Win7, yet at work it works fine for you... on XP! Not sure if that's really the problem or not, but just thought I'd point it out. |
||||||||||||||
|
|
|||||||||||||||
|
uker
|
This morning I had the idea to uninstall/reinstall all of the adobe software but it did not help. Still the same symptoms. Chrome includes a version of flash player in its build, so I could't completely reinstall that one, but then again, it's not just a Chrome problem for me. Since it may be W7 problem, maybe there is a security setting that isn't letting Sandboxie read what it needs to function correctly. Then again, it had been running smoothly for me for more than a year now, so it would have to be a change made in Sandboxie within the last few builds.
|
||||||||||||
|
|
|||||||||||||
|
tzuk
|
Not really sure what to tell you. As you said, Chrome doesn't use the same plugin for Flash as Firefox, these are different plugin files in different locations so it's strange that both stopped working at the same time. Can you post your Sandboxie.ini file? I'd like to make sure all the settings look good.
|
||||||||||||
|
|
|||||||||||||
|
uker
|
tzuk - here's my .ini file:
[GlobalSettings] Template=ScreenReader Template=AdobeAcrobatReader Template=AVG_Anti_Virus [DefaultBox] ConfigLevel=7 AutoRecover=y Template=BlockPorts Template=LingerPrograms Template=Firefox_Phishing_DirectAccess Template=AutoRecoverIgnore RecoverFolder=%{374DE290-123F-4565-9164-39C4925E467B}% RecoverFolder=%Personal% RecoverFolder=%Favorites% RecoverFolder=%Desktop% Enabled=y [UserSettings_1E080359] SbieCtrl_NextUpdateCheck=865295052699 SbieCtrl_UpdateCheckNotify=y SbieCtrl_ShowWelcome=n SbieCtrl_HideWindowNotify=n SbieCtrl_WindowLeft=200 SbieCtrl_WindowTop=150 SbieCtrl_WindowWidth=660 SbieCtrl_WindowHeight=450 SbieCtrl_ActiveView=40021 SbieCtrl_BoxExpandedView_DefaultBox=y |
||||||||||||
|
|
|||||||||||||
|
tzuk
|
Thanks. Try turning off both AdobeAcrobatReader and ScreenReader and let's see if this has any effect on your problem.
|
||||||||||||
|
|
|||||||||||||
|
SnDPhoenix
|
Hey just a little update.
I have noticed that the last few nightly and dev builds of Chrome/Chromium have NOT had this "Unresponsive" issue! I haven't made any changes to my computer or Sandboxie, except updating to newer builds of Chrome/Chromium as they're released. I think the problem may have been related to Chrome and not Sandboxie. Looking through their changelogs, you can see stuff like "Flash Player sandboxing has been temporarily moved behind a flag", "Flash Player sandboxing has been restored", "Flash Player sandboxing has been restored for all platforms but XP", "Due to stability issues Flash Player sandboxing has been put behind a flag for 9.0", etc.. and yes, those are actual quotes taken from the changelogs over the last couple weeks... which is incidentally the same time I started having these problems (if I remember correctly). Therefore to reiterate, I believe the problem with Flash was caused by Chrome and the problem was just manifesting itself in Sandboxie in my case. |
||||||||||||
|
|
|||||||||||||
|
tzuk
|
That sounds reasonable for the Chrome issue, and even more so, considering the problem disappeared for you SnD.
But it doesn't explain why Flash should misbehave in Firefox... Which is a different issue of course. |
||||||||||||
|
|
|||||||||||||
|
SnDPhoenix
|
That is true tzuk, though remember that the issue with Flash + Firefox is unique to uker (thus far) and nobody else (myself included) have reproduced any Flash related issues in Firefox, so it very well may just be some other fluke on his system causing the issue and not Sandboxie, such as in my case where Chrome seems to have been the issue all along. |
||||||||||||||
|
|
|||||||||||||||
| the following plug-in is unresponsive: Shockwave Flash |
|
||
|


Use the RSS feed to watch this topic for replies