Ok this is my result with the extra settings added to the file. Redtube seemed to behave the same as before with no problems. Megaupload had fluctuating CPU but higher than before - it also stayed at 99% longer than before. So we need a confirmation on Firefox with the settings on this site megaupload.com



mitch

Thats how my ini file looks. I've tried omitting the 4 ClosedFilePath arguments but CPU usage was still high.

What happened to the Wraithdu setting? Also why do I not see forceprocess=firefox.exe? Have you been not in fact sandboxed through all this?

Wraithdu's OpenFilePath didnt have any effect on things (I've tested with the settings in 5 times) so I removed it. I'm using the unregistered version so no use in having that Force setting if its not active...

Well, if you have chosen to not have an openfilepath to your plug-ins directory, and are having trouble with a site heavily dependent on at least two of those plug-ins ... could be more of an uphill battle - any good Firefox guys out there?
mitch

From googleing about in even a casual way Flash problems are out there. I think that if you have a perfect machine in every form (which of course is no one) things are fine.

But if there is anything about the setup that varies from the norm at all there seem to be problems. And I think that adding Sandboxie to the equation in those situations only heightens those problems.

The thing is that many times users do not notice there is a problem because things "work". Then when they install sandboxie, whatever the underlying symptom is is heightened and noticeable and so the complaint that "Sandboxie did it". I'm not trying to defend Sandboxie here, but the problem can not be reproduced consistently enough for a conclusion.
mitch

Hmm, i just noticed something, you say you have 3.01 installed right? But which 3.01 is it, is it the "Final" 3.01 build, or is it the "Experimental" 3.01 build, if its the "Final" build, then maybe you could try installing the "Experimental" build to see if it helps any?

A couple things I'd like you to try real quick. Change/add these -

BoxRootFolder=C: (no trailing backslash)

OpenFilePath=firefox.exe,C:\Program Files\Mozilla Firefox\plugins
OpenFilePath=firefox.exe,C:\WINDOWS\system32\Macromed

Try this out with the newest exp build, 3.01.21, and be sure to refresh your config if you change the INI while SB is running. I just wanna be sure all bases are covered, then I'm out of suggestions at the moment.

I'm embarrassed to say this but where can I get the experimental version from? I couldnt locate it on the download page and a search for "3.01.21" yields nothing


This is how my ini file looks now, I've added your modifications wraithdu, but I cant see an improvement over the older ini in terms of CPU usage (tested with megaupload).

See the "Announcement: Latest Experimental Version..." message in this same "Official Version 3.00 and Later" forum.

I suppose that I should clarify a little here -

the OpenFilePath settings I mentioned do not necessarily eliminate the higher than usual CPU usage while on the megaupload site. I still see CPU spikes from time to time, and an average around 40-60% (this is on a newer laptop). However these additions do prevent FF from freezing up, which is what it used to do, requiring Task Manager to end the process. If you're saying that FF no longer freezes when on megaupload, then I wouldn't hold out for much more progress.

So I guess the quesiton is, does FF still freeze up on you? Or can you use it now, albeit with higher CPU usage?

Ok ive tried with the experimental build and the same ini I posted a few posts back but still no luck.

@ wraithdu Firefox was never "freezing" and I could close it or navigate to a different site both via the address bar and the bookmarks. The "problem" is CPU usage jumping to 90%++ while megaupload was open (extreme, it would only increase by 30% for youtube for example).

@ mitch I was never concerned with memory issues as sandboxie didnt seem to have an impact on Firefox's memory usage.

Well now you're contradicting yourself. In your first post you said -

Did I misinterpret? If FF was never "freezing", then this post would be about half the length it is now. Good luck.

I think I was not letting the page load all the way, it does freeze for a couple of seconds (can even get to as much as 20) but it does respond afterwards but keeps the CPU usage high