"Not responding" upon downloading files

[bjm]

http://forums.sandboxie.com/phpBB3/view ... 05#p118917

Re: Firefox crashes after downloading files
Postby FredF2 » Tue Mar 08, 2016 6:24 pm
Re: Mozilla on various threads they maintain have suggested 32 bit FF solves the problem
I'm on w8.1 64 bit, and just switched to ff 32 bit... seems to have cleared up the problem for me so far.

5.11.5 -- W8.1 64bit, FF46 32/64bit sandbox, random... "Not responding" upon downloading files.
Just feedback.
Regards

[Craig@Invincea]

Thanks. We'll see if we get more reports. We haven't used 46 that much yet.

[Bertus]

sandboxie 5.11.6 (64bit) seems to fix my "not responding" problem with firefox (cyberfox).
system: Windows 8.1 64bit
browser firefox 46.0 (32bit), cyberfox 46.0 (32bit)

[bjm]

sandboxie 5.11.6 (64bit) seems to fix my "not responding" problem with firefox (cyberfox).
system: Windows 8.1 64bit
browser firefox 46.0 (32bit), cyberfox 46.0 (32bit)

Yes, 32bit random "Not responding" is a lot less vs. 64bit.
I commented in the earlier topic that I thought my "Not responding" started with FF42x64.
I've been trying to convince myself since FF42 that 64bit is better.
After FF46 update, and continued 64bit "Not responding" and an issue with other program. I'm back with 32bit.
I still have an occasional, random "Not responding" with 32bit, albeit harder to reproduce vs. 64bit.
Common is sandbox. Outside sandbox I cannot reproduce "Not responding".
We know Firefox is not perfect (nor my setup) and I'll work around my "Not responding" upon download with download manager/accelerator.
Thank you Bertus and Thank you Craig@
Cheers, Happy to read "5.11.6 seems to fix".

[bjm]

5.11.6 seems to fix.
What changed in 5.11.6
fingers crossed
Namaste

[Craig@Invincea]

5.11.6 seems to fix.
What changed in 5.11.6
fingers crossed
Namaste

Nothing related to this directly. It was a win10 and some WOW64 things, but maybe it Cascaded?

[bjm]

5.11.6 seems to fix.
What changed in 5.11.6
fingers crossed
Namaste

Nothing related to this directly. It was a win10 and some WOW64 things, but maybe it Cascaded?

my bad....what changed was rhetorical....cascade