Cumulative Update KB4517211 Windows 10 v1903 build 18362.387 Sept. 26 Win Update

I guess sometimes when I have some tabs open I just like to close out and start over. Which normally works fine (except so far on Amazon). I'm also just a very quick mouse user in general. I guess it's my use style. Some people like a lot of tabs open and actually keep them open. I do not like clutter and do not like to do that. I like speed. In any case, imo, it should not be hanging like that. No other browser does that. When I close the browser, or any program, I want it to close within a second of hitting the X. That's what closing is.

Instead of me changing the way I use it.. which I could do, i'd just like it to work like other browsers and not hang.

That said, I have a friend who does not use the browser like that and still runs into it occasionally just in natural use. I'd like to stop that from happening if possible. I'll figure something.

tomseys said:

I've tried all of those things except for using 32bit FF. I've also reduced the content processes to 1 or 2, turned off hardware acceleration (I also complete uninstalled flash and reinstalled it) and it makes no differences. I think I've read that FF will be removing the ability to turn off e10 in future... not sure if that is accurate.

If I turn off javascript on my uBO on the amazon domain the issue vanishes.

Just recently, Mozilla made disabling E10s difficult but it still can be done. Look at the pictures below.






Bo

tomseys said:

I guess sometimes when I have some tabs open I just like to close out and start over. I'm also just a very quick mouse user in general. I guess it's my use style. Some people like a lot of tabs open and actually keep them open. I hate clutter and do not like to do that. I love speed. In any case, imo, it should not be hanging like that. No other browser does that. I'm going to fix it. I've done it before. Thanks.

I guess what I'm trying to say is that I don't think it's about Amazon particularly at all, and you're not going to 'fix' it - it's just the way FF shuts down. I'll bet Mozilla addresses it by and by - especially if you lodge a complaint with them instead of on a Win10 forum. You seem a bit overly bothered by this - why not just use another browser if it's that important to you? Or, you could just relax - it's Friday night, have a beer, whatever

tomseys said:

Well I haven't found any other sites that do that yet... but no biggie, just curious if others have seen it or know fixes. Have a great night!

Thanks for your suggestions as well bo elam.. I'll look at those. Thanks!

G'night!

tomseys said:

Yes, this works.

I disabled e10s using an environmental variable with info I found online. With FF 64 bit.

Now the browser works perfectly with no hangs anywhere (amazon, google maps etc). Also the browser is noticeably faster in general. Wish they made the browser like this! I've read that disabling e10s makes FF less secure though.

It's funny now I remember when the issue happened years ago it was almost the same solution except I believe it disabled the plugin container.

Anyway, I'll see how it goes but for now, thanks again.

You are welcome, tomseys. Regarding security, the Firefox sandbox works along Multiprocess, so, if you disable MP, the sandbox is also disabled. For you, is a trade off. By disabling MP, you are getting stability which you didn't have, but you lose the small amount of security that the Firefox sandbox gives you. IMO, since you are experiencing the Firefox still running glitch constantly, making using the browser very inconvenient, this trade off, is worth it.

Bo