You're using developer edition (based on the > 12, restarting the browser has a chance to have the browser hang or > From what I can tell, January 11 was the last good build. > (In reply to David Smith from comment #4) (In reply to :Gijs Kruitbosch from comment #5) Resetting and then restarting the browser (even if I can manage an immediate restart) has them back in the state where electrolysis is not allowed. Some of the original failures occurred with electrolysis enabled, but recently electrolysis has remained off (and the hangs and quits continue), because I can no longer reset the accessibility flags that forcibly disable electrolysis. However, for those five crashes, I've probably had a hundred instances of hangs and quits that were never reported. They all seem to relate to one of two functions: RtlpLowFragHeapAllocFromContext, and RtlpLowFragHeapFree. However I did have a period where I was able to get a crash report sent. This rarely causes crashes, preferring to either hang or quit.
The next check of the About box will cause a new download of the update, and prompt for another restart attempt.
When this happens during a daily update, the update is not installed. Requires forcibly ending the process.Ī typical restart requires 4 to 6 attempts of the program self-quitting or hanging, before the browser can manage to completely load and run. Requires forcibly ending the process.Ĥ) Program gets to somewhere between 20 MB and 60 MB, then hangs. Memory noted is Working Set as listed in the Resource Monitor program.ġ) Program gets to about 4 MB, then self-quitsĢ) Program gets to about 15 MB, then self-quitsģ) Program gets to about 15 MB, then hangs.
No new device drivers have been added recently. The fewer addons installed, the more likely the program is to succeed on restart, so I typically do updates from a temp profile. If that's the case, they didn't mess up, your theme creator is just slow.User Agent: Mozilla/5.0 (Windows NT 6.1 WOW64 rv:45.0) Gecko/20100101 Firefox/45.0Īttempting to start browser, either from scratch, or restarting after an update becomes available, or restarting after enabling/disabling certain addons.ġ) Complete uninstall/reinstall of firefoxĤ) Use a complete, brand-new temp profile Last edited by gregfrankenstein ( 21:59:56) I never thought I'd wish for a browser that runs on Qt. The settings menu in Cheese is- I don't even know what's going on. If I'm prompted for the GNOME keyring password, I'm typing into a non-existent text box. Same with the HTML buttons in Firefox, like the "submit" button at the bottom of this reply page. The "save changes to document" window in gedit has no distinguishable buttons, only stray text that functions as a button. I just made a typo while writing this and had a heck of a time trying to replace those couple words. Functionally I can select text, but I can't actually see what I'm selecting. Both Firefox and gedit have invisible scroll bars and text highlighting won't show up. I don't use GNOME as an environment, but any GNOME-based app is glitched like crazy. I don't know about system wide, but it's not just Firefox. For info, these are NOT system wide problems, and only seem to affect FF.