#1444547 [Core:DOM: Device Interfaces]-Abort with InvalidStateError when allowCredentials is empty but the user touches a token anyway [All][[webauthn] [webauthn-interop]]
#1445419 [Core:DOM: Events]-AsyncPanZoomController::CanScroll mistakenly called CanScrollWithWheel without distinguishing between wheel scrolling and non-wheel scrolling [Uns][]
#1440701 [Core:DOM: Security]-Telemetry for browser upgrade failure rates [All][[domsecurity-active]]
#1445217 [Core:DOM: Workers]-Cleanup WorkerControlRunnable in dom/fetch [Uns][]
#1445594 [Core:DOM: Workers]-Fetch can trigger a crash releasing a Promise object on the wrong thread. [Uns][]
#1445540 [Core:DOM: Workers]-Use WorkerRef in some more dom classes [Uns][]
#1437438 [Core:DOM]-Add counters in DocGroup and WorkerPrivate to track their activities [Uns][[perf-tools]]
#1445592 [Core:JavaScript Engine: JIT]-Generate LOpcodes.h and MOpcodes.h at compile-time [All][]
#1437532 [Core:JavaScript Engine]-PodOperations.h:32:9: warning: 'void* memset(void*, int, size_t)' clearing an object of non-trivial type 'struct JS::TabSizes'; use assignment or value-initialization instead [-Wclass-memaccess] [Uns][]
#1443091 [Core:Widget: Gtk]-[GTK] IMContextWrapper shouldn't treat KeyboardEvents as "processed by IME" if it's handled as dead key [Lin][]
#1444571 [Core:Widget: Gtk]-[GTK][IIIMF] Make IMContextWrapper::PrepareToDestroyContext() GTK3-aware [Lin][]
#1444572 [Core:Widget: Gtk]-[GTK][uim] Dispatch fake "keydown" and "keyup" events if active IM uses key snooper and send some preedit signals to us [Lin][]
#1445533 [Core:XPCOM]-Avoid unnecessary ref-count in MozPromise::Steal() [Uns][]
#1445584 [Core:XPCOM]-add a move assignment operator for nsCOMPtr [All][]
#1445153 [Firefox:Developer Tools: Computed Styles Inspector]-Remove remaining references to the boxmodel appearing in computed view [Uns][]
#1445772 [Firefox:Developer Tools: Console]-Remove console.log.bind(console) pattern in tree [Uns][]
#1443457 [Firefox:Developer Tools: Console]-Stop referencing the "addon-sdk" loader in devtools code [All][]
Well, it auto-updated, and this time it went up a version to "60.0b3 (64-bit)".
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:60.0) Gecko/20100101 Firefox/60.0 ID:20180312152746
It seems to not only not have helped with memory issues, but it seems to have gotten worse! It is back to the system-killing memory suck. Right now, I have two windows open with maybe 25 tabs total. Windows Task Manager has 5 processes, all of them are the top memory consumers, the biggest being 1,066,968K. It brings my system to a stop, then it comes back again later. Usually, the only thing to fix this is to kill and restart all Firefox processes.
This morning I updated and then updated again. Afterwards several saved tabs turned into new tab pages and I lost the content. (Pinned tabs were fine.) As recently as a couple of days ago I left tabs in my session and they were correctly restored on restart, but I don't recall the last time I did a double update.
Is there a bug report for this behavior? A Bugzilla search using the keywords I would have used didn't find it.
(Please pardon me if this was discussed recently. I've been traveling and visiting relatives.
TheVisitor wrote:Yes, sadly it won't make today's Nightly - will be in the one tonight. Unless somehow , someone could convince them to re-spin.
The next (tonight's) Nightly should also have the fix for Webrender flickering on Nvidia cards. Looking forward to it!
I installed the flickering patch that is on inbound. It finally gets rid of the flickering. Now they need to get rid of the slight delay when starting Fx and the apparent darkening of fonts on some sites.
Intel i9-13900K | ASUS ROG MAXIMUS Z790 HERO DDR5 | 64GB CORSAIR VENGEANCE DDR5 @ 6600 Mhz.
H100i ELITE CAPELLIX XT Liquid CPU Cooler | PNY 12GB GeForce RTX 3080 Ti | 2 CORSAIR 2TB MP600 PRO XT GEN 4
HX1200 PLATINUM PSU | XENEON 32" IPS UHD 144Hz | BenQ 32" UHD | MS Windows 11 Pro
streetwolf wrote:I installed the flickering patch that is on inbound. It finally gets rid of the flickering. Now they need to get rid of the slight delay when starting Fx and the apparent darkening of fonts on some sites.
Most font rendering work is planned for Nightly 61 (or was it 62?).
WaltS48 wrote:Just got the update to the 2nd Official 20180315 Nightly on Linux, and the only thing that works is Ctrl+Q to Quit the application.
Update at your own risk.
File->Exit WFM as well as hitting the 'X' in upper right corner.
I do notice that starting the browser now it opens in a small window in upper left before flipping to maximized (the way I always run my apps).
Not too jarring but not right either IMO.
TheVisitor wrote:I do notice that starting the browser now it opens in a small window in upper left before flipping to maximized (the way I always run my apps).
Not too jarring but not right either IMO.
Confirmed.
Ray
OS'es: 4 computers with Win10 Pro 64-bit; Current Firefox, Beta, Nightly, Chrome, Vivaldi
WaltS48 wrote:Just got the update to the 2nd Official 20180315 Nightly on Linux, and the only thing that works is Ctrl+Q to Quit the application.
Update at your own risk.
File->Exit WFM as well as hitting the 'X' in upper right corner.
I do notice that starting the browser now it opens in a small window in upper left before flipping to maximized (the way I always run my apps).
Not too jarring but not right either IMO.
My Windows Nightly is okay, don't know about Mac's.
Linux is broken even with a new profile.
Linux Desktop - AMD Athlon(tm) II X3 455 3.3GHz | 8.0GB RAM | GeForce GT 630 Windows Notebook - AMD A8 7410 2.2GHz | 6.0GB RAM | AMD Radeon R5
mozillaZine is an independent Mozilla community and advocacy site. We're not affiliated or endorsed by the Mozilla Corporation but we love them just the same.