MozillaZine

The Official 20170516 builds are out

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

Post Posted May 15th, 2017, 4:23 pm

Previous Nightly Builds thread 20170515

The Official 20170516 NIGHTLY builds are out
The Official Firefox 54 Beta 8 builds are out

Previous NIGHTLY: 20170515 (Fx 55.0a1)
Previous BETA: 20170512 (Fx 54.0b7)

Tinderbox Builds
Treeherder
Release Notes: NIGHTLY | BETA
Changelogs: NIGHTLY | BETA


Fixed:
    NIGHTLY +38
  1. #1343638
  2. #1364001 [Core:Audio/Video: Playback]-Don't throttle readahead until download is fast enough [Uns][]
  3. #1363699 [Core:CSS Parsing and Computation]-Make named CounterStyle not refcounted [Uns][]
  4. #1364824 [Core:CSS Parsing and Computation]-stylo: Implement PostRebuildAllStyleDataEvent [Uns][]
  5. #1350175 [Core:CSS Parsing and Computation]-stylo: Support getting line / column number of CSS rules [Uns][]
  6. #1361823 [Core:DOM: Workers]-Intermittent browser_scratchpad_wrong_window_focus.js | application crashed [@ ScriptLoaderRunnable::LoadScript] [Uns][[stockwell needswork]]
  7. #1364589 [Core:DOM]-AppendDocumentLevelNativeAnonymousContentTo should include the custom content container [Uns][]
  8. #1364814 [Core:Editor]-Use RAII class to set and restore editor flags [Uns][]
  9. #1364161 [Core:Gecko Profiler]-GCMajor markers seem off [All][]
  10. #1343482 [Core:Graphics]-gfx-labeling Label runnables in gfxCrashReporter. [Uns][[gfx-noted][QDL][BACKLOG][GFX]]
  11. #1355441 [Core:HTML: Parser]-Don't allocate HTML5StackNodes all the time from heap [Uns][]
  12. #924058 [Core:JavaScript Engine]-Array operations should use ToLength on user-supplied indices, not ToUint32 [Lin][]
  13. #1362753 [Core:JavaScript Engine]-Array.prototype.slice and Array.prototype.splice should always take the fast path for non-Array native objects [Uns][]
  14. #1364442 [Core:JavaScript Engine]-Profiler JSON is broken depending on the OS locale because float values (used for minor GC timing) can use the wrong decimal separator [All][]
  15. #1354455 [Core:Networking]-Intermittent Assertion failure: mEventQueue.IsEmpty() || (needResumeOnOtherThread || mSuspended || !!mForcedCount), at ChannelEventQueue.cpp:91 [Uns][[necko-active][PBg-HTTP-M3]]
  16. #1363876 [Core:Plug-ins]-Enable async drawing for 64-bit builds in 54 and higher [Uns][]
  17. #1362303 [Core:Widget: Cocoa]-Crash in IPCError-browser | SHMEM_CREATED_MESSAGE Payload error: message could not be deserialized [Mac][]
  18. #1359490 [Core:XPCOM]-abstract away event loop spinning [All][]
  19. #1345349 [Firefox:Bookmarks & History]-Bookmark keywords cannot be used or updated if a keyword points to an invalid url [Uns][[fxsearch]]
  20. #1364860 [Firefox:Developer Tools: JSON Viewer]-JSON with error produces horizontal scrollbar [Uns][]
  21. #1364453 [Firefox:Developer Tools]-DevTools: move debugging intermittents documentation into the tree [Uns][]
  22. #1362103 [Firefox:General]-Suppress window animation on first window opening [Uns][[photon-performance]]
  23. #1363291 [Firefox:General]-[jsplugins] Handle save to file when printing pdf without e10s failed [Uns][]
  24. #1364571 [Firefox:Sync]-Delay Weave import [Uns][]
  25. #1355663 [Firefox:Sync]-Don't de-duplicate tabs from multiple devices [Uns][]
  26. #1362510 [Firefox:Sync]-Remove services/sync/locales/en-US/errors.properties [Uns][]
  27. #1364166 [Firefox:Theme]-Combined toolbar buttons don't have toolbarbutton-1 class after opening the menu panel [Uns][[photon-structure][p2]]
  28. #1364702 [Firefox:Theme]-Forward button looks like Back button in RTL locales [Uns][[photon-visual][p1]]
  29. #1352366 [Firefox:Theme]-Implement new location and search bar appearance [All][[photon-visual][p1][57]]
  30. #1363739 [Firefox:Theme]-Remove search-arrow-go-rtl.svg [All][]
  31. #1361686 [Firefox:Theme]-Share bookmark toolbar button styling between platforms [Uns][[photon-visual][p4]]
  32. #1363753 [Firefox:Toolbars and Customization]-Ensure that the width of panel views do not exceed that of the main view [Uns][[photon-structure]]
  33. #1364878 [Toolkit:Add-ons Manager]-All extensions are force enabled and marked as disabled in about:addons & about:support in Mozilla Firefox Nightly 55.0a1 (2017-05-15) [Win][]
  34. #1362384 [Toolkit:Downloads API]-Remove code to import data from "downloads.sqlite" [Uns][]
  35. #1359978 [Toolkit:Form Manager]-[Form Autofill] Implement the credit-card storage [All][[form autofill:M3]]
  36. #1322523 [Toolkit:Safe Browsing]-Add telemetry probe to see the distribution of prefix lengths in matches [Uns][#sbv4-m7]
  37. #1333328 [Toolkit:Safe Browsing]-Refactor cache miss handling mechanism for V2 [Uns][#sbv4-m7]
  38. #1362047 [Toolkit:WebExtensions: General]-Borderify webextension is broken [All][[content scripts], investigating]

    Partial Landings/Diagnostic Patches:
  1. #1363027 [Core:Disability Access APIs]-Crash in mozilla::a11y::Accessible::RemoveChild [Win][[clouseau]]
  2. #1364911 [Firefox:Toolbars and Customization]-Wait for the history subview to be populated before opening it [Uns][]

    Beta 7 -> Beta 8 Changelog +20
  1. #1342567
  2. #1361098
  3. #1361100
  4. #1358868 [Core:Audio/Video: cubeb]-Crash in `anonymous namespace''::wasapi_stream_start [Win][]
  5. #1358896 [Core:Audio/Video: cubeb]-Crash in audiounit_setup_stream [Mac][]
  6. #1357040 [Core:Audio/Video: Playback]-Crash in mozilla::MP4Demuxer::NotifyDataArrived [Lin][]
  7. #1361756 [Core:Audio/Video: Playback]-WebM video format not working if site triggers network download for invisible media elements [Uns][]
  8. #1355480 [Core:DOM]-Add telemetry for measuring the average load caused by timeouts [All][]
  9. #1334583 [Core:DOM: Animation]-WebAnimation crash: Assertion failure: !IsNull() (Cannot compute with a null value) [@mozilla::EnableIf] [Mac][]
  10. #1357692 [Core:Graphics]-High CPU usage and jerky animation on Firefox 53 [Win][]
  11. #1161312 [Core:JavaScript Engine]-Crash with heap-buffer-overflow [@ js::frontend::TokenStream::TokenBuf::getRawChar()] [Lin][[jsbugmon:][fuzzblocker]]
  12. #1361520 [Core:JavaScript Engine]-Disable SharedArrayBuffer in Fx54 [Uns][]
  13. #1363431 [Core:JavaScript Engine: JIT]-wasm: Check maximum size of br_table [Uns][]
  14. #1360574 [Core:Networking]-Firefox stops working after 900 connections when using NTLM proxy [All][[necko-active][ntlm]]
  15. #1363472 [Core:Networking]-Crash in mozalloc_abort | NS_DebugBreak | mozilla::ipc::FatalError | mozilla::net::PNeckoChild::SendPWyciwygChannelConstructor [Win][[necko-active]]
  16. #1361787 [Core:Printing: Output]-Printing hang with box-shadow on windows 10 [Win][]
  17. #1359411 [Core:Selection]-something in JS application or TinyMCE hangs Firefox completely [All][regression]
  18. #1363563 [Core:WebRTC: Networking]-Firefox crashes when using WebRTC and renegotiating with a new offer that has less RTP header extensions than the previous one. [Uns][regression]
  19. #1362493 [Firefox:General]-e10s beta cohort distribution improvements [Uns][]
  20. #1363262 [Toolkit:Startup and Profile System]-Crash in mozilla::detail::nsStringRepr::First (called from nsCommandLine::HandleFlagWithParam) [All][]

Nightly 55 fixes since 20170306 (Gecko 54) ~3520
Beta 54 fixes since 20170123 (Gecko 53) ~2563

Nightly Blog
Release Calendar
Release Tracking
Last edited by Josa on May 16th, 2017, 2:06 pm, edited 1 time in total.

Omega X

User avatar
 
Posts: 7774
Joined: October 18th, 2007, 2:38 pm
Location: A Parallel Dimension...

Post Posted May 16th, 2017, 3:46 am

Apparently, Mozilla gave up on Jemalloc4.
Latest: Firefox/53.0.3 *ESR/52.1.0 - Mobile/53.0.3 - Thunderbird/52.1.1 - SeaMonkey/2.46
Nightly: Nightly/55.0a1 - Mobile/55.0a1 - Daily/52.0a1 - SeaMonkey/2.49a1

Arch5

User avatar
 
Posts: 1063
Joined: April 11th, 2014, 7:34 pm
Location: Melbourne Australia

Post Posted May 16th, 2017, 4:10 am

Omega X wrote:Apparently, Mozilla gave up on Jemalloc4.

https://bugzilla.mozilla.org/show_bug.cgi?id=762449#c65

koboltzz
 
Posts: 19
Joined: December 22nd, 2015, 3:17 am

Post Posted May 16th, 2017, 5:25 am

Anybody still encouter video artifacts?

marty60
 
Posts: 425
Joined: March 21st, 2012, 7:09 am

Post Posted May 16th, 2017, 5:37 am

Does bug 1364878 address the fact that when addons are disabled by choice they are not completely disabled anymore and are still using memory?

https://bugzilla.mozilla.org/show_bug.cgi?id=1364878

For example, normally stylish is kept disabled because it tends to use a lot of memory and only enabled if I want to do work in real time, otherwise userContent.css is good enough. In these latest nightlies you can still access some stylish settings and memory usage is back up despite being disabled. Just to confirm, I also temporarily disabled CTR and all of its settings are still there being used. Is this intentional and do we now have to uninstall addons to completely disable them?

sciguyryan
Folder@Home

User avatar
 
Posts: 2054
Joined: November 10th, 2004, 1:33 pm
Location: Wales

Post Posted May 16th, 2017, 6:00 am

Looks like they'll just stick with jemalloc 3 then? That's an interesting decision. Though given all the problems with trying to upgrade it I can understand why.
Visit My Blog if you want to hear more.

Ryan Jones

WaltS48

User avatar
 
Posts: 3165
Joined: May 7th, 2010, 9:38 am
Location: Pennsylvania, USA

Post Posted May 16th, 2017, 6:18 am

marty60 wrote:Does bug 1364878 address the fact that when addons are disabled by choice they are not completely disabled anymore and are still using memory?

https://bugzilla.mozilla.org/show_bug.cgi?id=1364878

For example, normally stylish is kept disabled because it tends to use a lot of memory and only enabled if I want to do work in real time, otherwise userContent.css is good enough. In these latest nightlies you can still access some stylish settings and memory usage is back up despite being disabled. Just to confirm, I also temporarily disabled CTR and all of its settings are still there being used. Is this intentional and do we now have to uninstall addons to completely disable them?


I think users just need to wait for the bug fix to make it into the next Nightly and updates being enabled again.
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

marty60
 
Posts: 425
Joined: March 21st, 2012, 7:09 am

Post Posted May 16th, 2017, 6:27 am

WaltS48 wrote:I think users just need to wait for the bug fix to make it into the next Nightly and updates being enabled again.

It looks like bug 1364878 will take care of it since it's probably all related otherwise I'd file a separate bug. I'd hate to think that's intentional but with Mozilla these days you never know.

WaltS48

User avatar
 
Posts: 3165
Joined: May 7th, 2010, 9:38 am
Location: Pennsylvania, USA

Post Posted May 16th, 2017, 7:46 am

Firefox 54.0b8 has been released.

Mozilla/5.0 (X11; Linux x86_64; rv:54.0) Gecko/20100101 Firefox/54.0 ID:20170515194727 CSet: 9bef2dfbd584c0f3ae52953bfc3aed64e308960d

Edit: And once I post that news, this appears.

Nightly updates disabled in light of 1364878
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

GHM113
 
Posts: 337
Joined: December 16th, 2015, 3:59 am
Location: Moscow, Russia

Post Posted May 16th, 2017, 8:06 am

WaltS48 wrote:Edit: And once I post that news, this appears.
Nightly updates disabled in light of 1364878

What's the point to disable updates if bug 1364878 has already been fixed?
I am an idiot. Sorry for my poor English.

Peja Stija

User avatar
 
Posts: 501
Joined: June 4th, 2008, 8:46 am
Location: Belgium (proud producer of waffles)

Post Posted May 16th, 2017, 8:12 am

GHM113 wrote:
WaltS48 wrote:Edit: And once I post that news, this appears.
Nightly updates disabled in light of 1364878

What's the point to disable updates if bug 1364878 has already been fixed?

Never use the string "What's the point" in a Mozilla related discussion. [-X

smsmith
Moderator

User avatar
 
Posts: 19164
Joined: December 7th, 2004, 8:51 pm
Location: Illinois

Post Posted May 16th, 2017, 8:52 am

WaltS48 wrote:Edit: And once I post that news, this appears.

Nightly updates disabled in light of 1364878

Ahh... I was wondering why I had to manually update yesterday and auto-update isn't working today. Thanks!
Give a man a fish, and he eats for a day. Teach a man to fish, and he eats for a lifetime.
I like poetry, long walks on the beach and poking dead things with a stick.
Please do not PM me for personal support. Keep posts here in the Forums instead and we all learn.

Ver Greeneyes
 
Posts: 983
Joined: June 28th, 2008, 4:57 am

Post Posted May 16th, 2017, 8:52 am

Omega X wrote:Apparently, Mozilla gave up on Jemalloc4.


As someone who has been involved in both trying to patch mozjemalloc and patching the glue code tying it all together: thank god. This stalemate was torture. I hope we can move forward now and make mozjemalloc less of a mess.

sciguyryan wrote:Looks like they'll just stick with jemalloc 3 then?


mozjemalloc is a heavily patched version of jemalloc 0.9 or something like that. The main thing setting it apart is that it can decommit unused pages inside runs - this was never upstreamed to jemalloc proper, and it's one of the reasons we were never able to switch.

WaltS48

User avatar
 
Posts: 3165
Joined: May 7th, 2010, 9:38 am
Location: Pennsylvania, USA

Post Posted May 16th, 2017, 9:11 am

GHM113 wrote:
WaltS48 wrote:Edit: And once I post that news, this appears.
Nightly updates disabled in light of 1364878

What's the point to disable updates if bug 1364878 has already been fixed?


Another bug or bugs.

bug 1365256 indicating that there's still issues even after the fix that was landed


Timestamp 16:03 at http://logs.glob.uno/?c=mozilla%23relen ... May%202017

It is Nightly. Not the Release version. :-k
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

sciguyryan
Folder@Home

User avatar
 
Posts: 2054
Joined: November 10th, 2004, 1:33 pm
Location: Wales

Post Posted May 16th, 2017, 9:13 am

Ver Greeneyes wrote:
Omega X wrote:Apparently, Mozilla gave up on Jemalloc4.


As someone who has been involved in both trying to patch mozjemalloc and patching the glue code tying it all together: thank god. This stalemate was torture. I hope we can move forward now and make mozjemalloc less of a mess.

sciguyryan wrote:Looks like they'll just stick with jemalloc 3 then?


mozjemalloc is a heavily patched version of jemalloc 0.9 or something like that. The main thing setting it apart is that it can decommit unused pages inside runs - this was never upstreamed to jemalloc proper, and it's one of the reasons we were never able to switch.


It's good to hear the reasons behind this sort of thing, we tend to only catch part of the story.

I assume that if there were any features that Mozilla wanted from newer jemalloc versions that they could cherry pick them anyway, right?
Visit My Blog if you want to hear more.

Ryan Jones

Return to Firefox Builds


Who is online

Users browsing this forum: No registered users and 3 guests