MozillaZine

The first official 20190525 builds are out

Discussion about official Mozilla Firefox builds
Josa
 
Posts: 4088
Joined: July 28th, 2009, 4:52 pm

Post Posted May 24th, 2019, 6:02 pm

Previous Nightly Builds thread 20190524

The first official 201905025 NIGHTLY builds are out
.The Official Firefox 68 Beta 5 builds are not yet out

Previous NIGHTLY: 20190524 (Fx 69.0a1)
Previous BETA: 20190524 (Fx 68.0b4)

Mozilla Inbound Builds
Treeherder
Release Notes: NIGHTLY | BETA
Changelogs: NIGHTLY | BETA


Fixed:
    NIGHTLY +58
  1. #1547472
  2. #1550633 [Core:Audio/Video: Playback]-[webvtt] HTMLTrackElement should not load resource when its text track is disable [Uns][]
  3. #1551385 [Core:Audio/Video: Playback]-[webvtt] cue display wasn't updated correctly when there are multiple cues with overlapping timestamp [Uns][]
  4. #1554347 [Core:CSS Parsing and Computation]-Sync servo stuff. [Uns][]
  5. #1554195 [Core:DOM: Bindings (WebIDL)]-Remove the MSG_THIS_DOES_NOT_IMPLEMENT_INTERFACE error message [Uns][]
  6. #1550613 [Core:DOM: Content Processes]-JSWindowActor crashes when sending messages early in lifecycle for in-process actors [Uns][]
  7. #1121623 [Core:DOM: Core & HTML]-Consider a better default for 'concrete' [mac][]
  8. #1553952 [Core:DOM: Core & HTML]-Fire oop-browser-crashed when mBrowserParent construction fails [Uns][]
  9. #1480236 [Core:DOM: Core & HTML]-Implement queueMicrotask() [Uns][]
  10. #1467625 [Core:DOM: Core & HTML]-Move domain attribute from HTMLDocument to Document [Uns][]
  11. #1554122 [Core:DOM: Core & HTML]-Rename nsAutoPopupStatePusher* and mark as MOZ_RAII [Uns][]
  12. #1553867 [Core:DOM: Core & HTML]-Time spent in ClonePrincipalForPermission() during pageload [Uns][[qf:p1:pageload]]
  13. #1551282 [Core:DOM: Web Authentication]-Pearson MyCloud breaks if FIDO U2F is not Chrome's implementation [All][]
  14. #1520166 [Core:DOM: Web Authentication]-Transition in-tree jcjones/u2f-hid-rs to vendoring mozilla/authenticator-rs v0.2.5 [All][[webauthn][u2f]]
  15. #1535835 [Core:Document Navigation]-Intermittent GECKO(2181) | Assertion failure: mGroup, at /builds/worker/workspace/build/src/docshell/base/BrowsingContext.cpp:188 [Uns][[stockwell unknown]]
  16. #1554065 [Core:Document Navigation]-nsDocShell::DoFindItemWithName seems to pass the wrong requestor to the TabGroup [Uns][]
  17. #1553259 [Core:Graphics: WebRender]-Allow WebRender for AMD devices with a battery, but running at low resolutions on nightly [Win][]
  18. #1533546 [Core:Graphics: WebRender]-DWrite contention on worker threads is too high [Uns][]
  19. #1553270 [Core:IPC]-Add a protocol name getter to IProtocol [Uns][]
  20. #1553874 [Core:Internationalization]-Assertion failure: false (MOZ_ASSERT_UNREACHABLE: should have been handled already), at /builds/worker/workspace/build/src/intl/lwbrk/LineBreaker.cpp:523 [Uns][]
  21. #1551796 [Core:JavaScript Engine: JIT]-Merge TypeScript and ICScript into JitScript [All][]
  22. #1552979 [Core:JavaScript Engine]-Allow modules to be compiled directly from UTF-8 [Uns][]
  23. #1553482 [Core:JavaScript Engine]-[BinAST] Expose the grammar to tokenizers to support reading Huffman tables [Uns][]
  24. #1554053 [Core:Javascript: WebAssembly]-Wasm via Cranelift: size of interrupt check comparison is incorrect [Uns][]
  25. #1553824 [Core:Layout: Grid]-Crash in [@ InvalidArrayIndex_CRASH | nsGridContainerFrame::GridReflowInput::PercentageBasisFor] [All][]
  26. #1553378 [Core:Layout]-devirtualize calls to GetText() / TextLength() when we know we have a Text node [Uns][]
  27. #1554137 [Core:Networking: Cookies]-nsICookie and nsICookie2 should be builtinclass interfaces [Uns][]
  28. #1551582 [Core:Panning and Zooming]-Scroll position jumps out-of-range on IRCCloud [All][]
  29. #1553318 [Core:Printing: Setup]-Remove nsIPrintSettings.kRangeFocusFrame [Uns][]
  30. #1553324 [Core:Printing: Setup]-Remove nsIPrintSettings.printFrameTypeUsage [Uns][]
  31. #1547813 [Core:Privacy: Anti-Tracking]-Implement a new cookie policy: block storage from trackers and partition all other third-party contexts [Uns][]
  32. #1551056 [Core:Privacy: Anti-Tracking]-get rid of BasePrincipal::CloneForcingFirstPartyDomain [Uns][]
  33. #1550531 [Core:SVG]--moz-element leaks memory and hangs whole browser with massive CPU usage at closing browser window with large image Theme after landing patch from bug #1330487 [Win][[qf:p2:resource]]
  34. #1383650 [Core:SVG]-Implement SVG geometry properties in CSS [Uns][[webcompat][wptsync upstream]]
  35. #1551185 [Core:Web Painting]-Contenteditable Div: Inline <img> in selection are not always highlighted [All][]
  36. #1531338 [Core:Widget: Gtk]-Current permission for block autoplay is not visible in Site information panel with high contrast enabled [Lin][]
  37. #1213601 [Core:Widget: Gtk]-Kinetic scrolling does not work on Linux [Uns][tpi:+]
  38. #1546832 [Core:Window Management]-Opening/Resizing developer tools causes incorrect content letterboxing [Lin][]
  39. #1553856 [Core:XPCOM]-LazyIdle threads should have names other than "LazyIdle" [Uns][]
  40. #1047408 [Core:XPCOM]-Remove nsTWeakRef [Lin][]
  41. #1552315 [Data Platform and Tools:Operations]-Rotate and hard code Prio public keys [Uns][[DataOps]]
  42. #1553278 [DevTools:Debugger]-"Download file" context menu not working properly [Uns][[debugger-mvp]]
  43. #1546109 [DevTools:Debugger]-Replace references to generatedLocation in the server [Uns][]
  44. #1554180 [DevTools:Debugger]-bad version of version of dwarf_to_json.wasm in the tree [Uns][]
  45. #1468402 [DevTools:Inspector]-Indent subgrids in the grid inspector sidebar [Uns][]
  46. #1552110 [DevTools:Netmonitor]-Wrong color for security values [Uns][]
  47. #1352070 [DevTools:Responsive Design Mode]-window.outerHeight returns wrong value in Responsive Design mode [Uns][[rdm-mvp]]
  48. #1542746 [Firefox Build System:General]-Switch clang-based PGO builds from front-end based instrumentation to IR-level instrumentation. [Uns][]
  49. #1554322 [Firefox:Activity Streams: Newtab]-[Export] Add accessible content, static clamping and bug fixes to Activity Stream [Uns][[export]]
  50. #1554148 [Firefox:Installer]-The "Re-install" button in not positioned correctly on some of the locale [Win][]
  51. #1552193 [Firefox:Search]-Search Telemetry reporting should match the codes that were used before the conversion to WebExtensions [Uns][]
  52. #1549831 [Firefox:Tracking Protection]-Set up an RPM handler for about:protections [Uns][]
  53. #1552780 [Toolkit:Add-ons Manager]-Abuse report panel should have a semi-transparent grey background [Uns][]
  54. #1541450 [Toolkit:Data Sanitization]-"Forget about this site" should clear site certificate exceptions [Uns][]
  55. #1550559 [Toolkit:Find Toolbar]-Convert findbar XUL textbox to HTML input [Uns][]
  56. #1553963 [Toolkit:Safe Browsing]-Safe Browsing doesn't cache the gethash result for V4 tables [Uns][]
  57. #1543861 [Toolkit:Storage]-consider auto-resizing map of LMDB environments for kvstore [Uns][]
  58. #1454192 [WebExtensions:Storage]-WebExtension storage permissions requested when Site Permissions are cleared on exit [Uns][]

    Partial Landings/Diagnostic Patches:
  1. #1510569 [Core:DOM: Content Processes]-Consider to rewrite WebProgressChild.jsm and RemoteWebProgress.jsm in C++ [Uns][[fxperf:p3]]
  2. #1553502 [Core:DOM: Workers]-Compile DOM worker scripts directly from UTF-8, behind a pref [Uns][]
  3. #1395509 [Core:JavaScript: GC]-Track the amount of malloc memory precisely [Uns][]

    Beta 4 -> Beta 5 Changelog +19
  1. #1548612
  2. #1549812
  3. #1551907
  4. #1552627
  5. #1552354 [Core:Audio/Video: Playback]-Video without audio ended too early before it really reaches to the end [Uns][]
  6. #1545842 [Core:CSS Parsing and Computation]-Downgrade a few release asserts to diagnostic asserts on beta. [Uns][]
  7. #1553286 [Core:DOM: Bindings (WebIDL)]-Mark legacycall hooks as MOZ_CAN_RUN_SCRIPT [Uns][]
  8. #1553400 [Core:DOM: Networking]-XMLHttpRequestDoneNotifier should own XHR, not vice-versa [Uns][[necko-triaged]]
  9. #1534394 [Core:Editor]-Crash [@get] near [@mozilla::WSRunObject::GetWSNodes()] [Uns][]
  10. #1550523 [Core:Graphics: WebRender]-Print preview not showing image on Animated .GIF, on Windows 10 with WebRender graphics backend [All][]
  11. #1551520 [Core:Graphics: WebRender]-1.53 - 3.93% displaylist_mutate (linux64-shippable-qr, windows10-64-shippable-qr) regression on push 73254a69497b209b372ed209ce9d004080ea8052 (Fri May 10 2019) [All][]
  12. #1550771 [Core:IPC]-Deadlock in SharedMemoryBasic_mach → AV1 playback doesn't work in Firefox Nightly on macOS 10.14.4 [Uns][]
  13. #1552987 [DevTools:Console]-Jump-to-function-definition buttons are no longer visible in the console [All][]
  14. #1552609 [DevTools:Debugger]-Adding a logpoint fails and breaks locations [Uns][[debugger-mvp]]
  15. #1552275 [DevTools:Inspector]-Copy link address from inspector doesn't work [Uns][[qa-triaged]]
  16. #1552302 [Firefox:Enterprise Policies]-Make notice in about:preferences about policies in use link to about:policies [Uns][]
  17. #1553226 [Toolkit:Crash Reporting]-Crash in [@ nsTSubstring<T>::Assign | CrashReporter::TakeMinidumpForChild] [Win][]
  18. #1552768 [Toolkit:Themes]-Input clear icon disappears on hover on Windows [Uns][]
  19. #1543384 [WebExtensions:General]-AsyncShutdownTimeout timeout in "Startup: Run manifest" [Uns][]

Nightly 69 fixes since 20190520 (Gecko 68) ~284
Beta 68 fixes since 20190318 (Gecko 67) ~2783

Nightly Blog
Release Calendar
Release Tracking
MozRegression Guide
Last edited by Josa on May 26th, 2019, 10:35 am, edited 1 time in total.

Are You A Wiiizard?
 
Posts: 394
Joined: August 30th, 2012, 4:27 am

Post Posted May 24th, 2019, 9:46 pm

What windows are you using?`
Are you on Windows 10 1903 18362.116?
If so try to update to windows insider version 18362.145 using the cab files and return
I updated to 18362.145 and the problem seems to be fixed so far,

I am but it started when I was on 1809. I really don't understand why updating to insider build and reverting to 1903 would fix it..?

jeny
 
Posts: 28
Joined: May 22nd, 2019, 11:55 am

Post Posted May 25th, 2019, 4:43 am

Are You A Wiiizard? wrote:
What windows are you using?`
Are you on Windows 10 1903 18362.116?
If so try to update to windows insider version 18362.145 using the cab files and return
I updated to 18362.145 and the problem seems to be fixed so far,

I am but it started when I was on 1809. I really don't understand why updating to insider build and reverting to 1903 would fix it..?


This is not an insider build, it is the same build 18362, just a preview, you don't need to go to insider ring!

Just install the CAB files, or wait a week and you will most likely get the same update.

Why update, for me it fixed the RAM leak issue, most likely cause Microsoft states that in this update they have addressed an issue preventing App from accessing D3D, it may be the reason.

https://blogs.windows.com/windowsexperi ... ild-18362/

TheVisitor
 
Posts: 4966
Joined: May 13th, 2012, 10:43 am

Post Posted May 25th, 2019, 5:12 am

Today's Nightly update was 23meg....

johnp_
 
Posts: 152
Joined: March 7th, 2011, 11:22 am

Post Posted May 25th, 2019, 5:51 am

Well, quite some stuff landed, but I suspect the switch to IR-level PGO instrumentation in preparation for PGO'ing Rust code changed code generation substantially.

Are You A Wiiizard?
 
Posts: 394
Joined: August 30th, 2012, 4:27 am

Post Posted May 25th, 2019, 10:31 am

jeny wrote:This is not an insider build, it is the same build 18362, just a preview, you don't need to go to insider ring!
Just install the CAB files, or wait a week and you will most likely get the same update.
Why update, for me it fixed the RAM leak issue, most likely cause Microsoft states that in this update they have addressed an issue preventing App from accessing D3D, it may be the reason.

It appears to be fixed (or at least less noticeable) for me in Nightly 25th build without updating Windows. Though I haven't really done any long browsing sessions but usually it leaked pretty fast and I'm not seeing any major memory growths in 45mins.

Virtual_ManPL

User avatar
 
Posts: 2001
Joined: July 24th, 2008, 5:52 am

Post Posted May 25th, 2019, 11:04 am

@ Are You A Wiiizard? - It could be:
Bug 1550531 - -moz-element leaks memory and hangs whole browser with massive CPU usage at closing browser window with large image Theme after landing patch from bug #1330487,
named before "Mozilla Firefox Nightly 68.0a1 uses too much CPU and sometimes even hangs for some time at closing browser window",
which is now fixed in latest build =D>
:monkey: 0X :banana:

Are You A Wiiizard?
 
Posts: 394
Joined: August 30th, 2012, 4:27 am

Post Posted May 25th, 2019, 11:34 am

Virtual_ManPL wrote:@ Are You A Wiiizard? - It could be:
Bug 1550531 - -moz-element leaks memory and hangs whole browser with massive CPU usage at closing browser window with large image Theme after landing patch from bug #1330487,
named before "Mozilla Firefox Nightly 68.0a1 uses too much CPU and sometimes even hangs for some time at closing browser window",
which is now fixed in latest build =D>
:monkey: 0X :banana:

Most likely, yeah.

Mark12547

User avatar
 
Posts: 288
Joined: May 13th, 2017, 11:36 am
Location: Oregon, United States, Earth

Post Posted May 25th, 2019, 12:57 pm

Virtual_ManPL wrote:@ Are You A Wiiizard? - It could be:
Bug 1550531 - -moz-element leaks memory and hangs whole browser with massive CPU usage at closing browser window with large image Theme after landing patch from bug #1330487,
named before "Mozilla Firefox Nightly 68.0a1 uses too much CPU and sometimes even hangs for some time at closing browser window",
which is now fixed in latest build =D>
:monkey: 0X :banana:


After last night's last update (presumably when Bug 1550531 had landed), after having played a number of YouTube videos, when I closed Firefox and the CPU went quickly to 0%, I thought something had gone wrong! No, Firefox had just closed normally!

It's weird how living with a problem for a couple of weeks change one's expectations! :D

Of course, paranoid me will still keep an eye out for this to verify that indeed the long CPU time at Firefox shutdown after playing a bunch of YouTube videos is indeed finally fixed! But, preliminarily it's a thumb's up for the Developers!

jeny
 
Posts: 28
Joined: May 22nd, 2019, 11:55 am

Post Posted May 25th, 2019, 3:04 pm

Are You A Wiiizard? wrote:
jeny wrote:This is not an insider build, it is the same build 18362, just a preview, you don't need to go to insider ring!
Just install the CAB files, or wait a week and you will most likely get the same update.
Why update, for me it fixed the RAM leak issue, most likely cause Microsoft states that in this update they have addressed an issue preventing App from accessing D3D, it may be the reason.

It appears to be fixed (or at least less noticeable) for me in Nightly 25th build without updating Windows. Though I haven't really done any long browsing sessions but usually it leaked pretty fast and I'm not seeing any major memory growths in 45mins.


Same thing, it is less noticeable not completely fixed with windows update

In fact, if the bug was not there, I will not notice it if I updated to FF beta 68 after the last windows update was released.

This is after 26 hours running and it is only 1.4GB RAM and 1,3 GB VRAM, the only noticeable is little bit VRAM usage

https://i.imgur.com/5MuO1mR.png
Last edited by DanRaisch on May 25th, 2019, 3:52 pm, edited 1 time in total.
Reason: Image tags removed to restore page formatting.

mdew

User avatar
 
Posts: 366
Joined: March 2nd, 2005, 2:34 am

Post Posted May 25th, 2019, 5:33 pm

Is there a way to turn off automatic updates?

Mouse4
 
Posts: 609
Joined: December 27th, 2017, 4:03 am
Location: Australia

Post Posted May 25th, 2019, 5:45 pm

mdew wrote:Is there a way to turn off automatic updates?

why do you wanna turn off automatic updates? thats the whole point of " Nightly "

but yeah you can turn them off, click in OPTIONS > HOME > Nightly Updates >

mdew

User avatar
 
Posts: 366
Joined: March 2nd, 2005, 2:34 am

Post Posted May 26th, 2019, 12:59 am

Because Nightly can break, and if you have control when it updates you won't update to a more broken build (if there is an issue)

Mouse4
 
Posts: 609
Joined: December 27th, 2017, 4:03 am
Location: Australia

Post Posted May 26th, 2019, 1:12 am

mdew wrote:Because Nightly can break, and if you have control when it updates you won't update to a more broken build (if there is an issue)

Microsoft Windows Updates Break stuff, i dont think you can turn that off. , but if thats what you want, i'd suggest you stay on the BETA Channel. or use Stable channel

mdew

User avatar
 
Posts: 366
Joined: March 2nd, 2005, 2:34 am

Post Posted May 26th, 2019, 1:22 am

Erm, I have run nightly for the last 15 years, and having control when it updates only has removed recently in the options. Using bleeding edge is fine, but even better when you can stick a previous build if things break. I'm actually surprised people don't do this already?

Return to Firefox Builds


Who is online

Users browsing this forum: No registered users and 3 guests