MozillaZine

The Official 20170621 builds are out

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

Post Posted June 20th, 2017, 7:34 am

Previous Nightly Builds thread 20170620

The Official 20170621 NIGHTLY builds are out
.The Official Firefox 55 Beta 4 builds are not yet out

Previous NIGHTLY: 20170620 (Fx 56.0a1)
Previous BETA: 20170620 (Fx 55.0b3)

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


Fixed:
    NIGHTLY +53
  1. #1371889
  2. #1374148 [Core:Audio/Video: Playback]-Crash in nvwgf2um.dll | CDecodeContext::BeginFrame [Win][]
  3. #1374275 [Core:Audio/Video: cubeb]-Update cubeb from upstream to 18153b9 [Uns][]
  4. #1371130 [Core:CSS Parsing and Computation]-stylo: descendant restyle hints not handled correctly in the presence of XBL [Uns][]
  5. #1373874 [Core:CSS Parsing and Computation]-stylo: two tests started leaking rule nodes over the last week [Uns][]
  6. #1370019 [Core:DOM: Animation]-Typo in KeyframeEffectReadOnly method "UpadateEffectSet" [All][]
  7. #1373857 [Core:DOM: Events]-The hashtable lookup in nsContentUtils::GetEventMessageAndAtom() can show up in profiles [Uns][]
  8. #1352278 [Core:DOM: Events]-[Pointer Event] Turn on PointerEvent preference on Mac and Linux nightly [Uns][]
  9. #1333651 [Core:DOM: Security]-Spoofing Navigator API when resisting fingerprinting is enabled [Uns][[tor][fingerprinting][domsecurity-backlog1][fp:m2]]
  10. #1362114 [Core:DOM]-Add telemetry to record the hit/miss of the JS start-up cache [Uns][]
  11. #1373555 [Core:DOM]-Move the Fetch consume body login in a separate class [Uns][]
  12. #1373222 [Core:DOM]-URL.createObjectURL crashes Firefox 54 [Uns][]
  13. #1374316 [Core:Disability Access APIs]-Add aria-readonly to switch, menuitemcheckbox, menuitemradio, and switch; remove aria-checked from menuitem [Uns][]
  14. #1374319 [Core:Disability Access APIs]-Bug 1366837 broke about:support on non-Windows OSes [Uns][]
  15. #1374643 [Core:Disability Access APIs]-Crash in mozilla::a11y::HandlerProvider::MarshalAs [Win][aes+]
  16. #1323069 [Core:Disability Access APIs]-Identification of remote a11y clients [Win][]
  17. #1357042 [Core:Disability Access APIs]-Implement or update support for exposure of aria-orientation [Lin][]
  18. #596501 [Core:Editor]-Make TextEditor::OutputToString faster [Mac][[post-2.0]]
  19. #1373381 [Core:Graphics: WebRender]-Update webrender to cset 1d6348023a4a4fdd89dce038640c5da906005acc (+ servo/webrender#1409) [Uns][[gfx-noted]]
  20. #1355746 [Core:HTML: Parser]-Parser should use idle dispatch and not a timer for background tabs [Uns][[qf:p1]]
  21. #1374625 [Core:Layout]-Protect ruby from crash because of failing to build text run [Uns][]
  22. #1374614 [Core:Layout]-Support SVG image context paint in XUL tree views (treecol etc.) [Uns][]
  23. #1369044 [Core:Networking: Cache]-Wrong assertion in AltDataOutputStreamParent::RecvWriteData [Uns][[necko-active]]
  24. #1374591 [Core:Networking: HTTP]-Progress value should reflect alt-data content length [Uns][[necko-active]]
  25. #1339027 [Core:Rewriting and Analysis]-remove useless declaration in VideoDecoderManagerParent.cpp [Uns][]
  26. #265894 [Core:SVG]-Support SVG CSS selector matching rules for <svg:use> [All][]
  27. #1374660 [Core:Security: Process Sandboxing]-Remove redundant declarations from content sandbox policy on macOS [Mac][]
  28. #1374440 [Core:WebRTC: Signaling]-max-message-size should only be emitted with EOR support [Uns][]
  29. #1372453 [Core:XPCOM]-Better naming for ProxyReleaseEvent [Uns][]
  30. #1374594 [Core:XPCOM]-Construct MonitorAutoUnlock from a MonitorAutoLock [All][]
  31. #833143 [Core:XPCOM]-Don't GC in nsXREDirProvider::DoShutdown() [Lin][]
  32. #1373271 [Firefox:Activity Streams: General]-Handle crashes in preloaded browsers in tabbrowser [Uns][]
  33. #1373492 [Firefox:Developer Tools: Inspector]-Enable the layout view [Uns][]
  34. #1370443 [Firefox:Developer Tools: JSON Viewer]-Empty objects not visible in JSON Viewer [Uns][]
  35. #1370139 [Firefox:Developer Tools: JSON Viewer]-TreeView path with slash hides another object [Uns][]
  36. #1280548 [Firefox:Developer Tools: Storage Inspector]-Don't display storage-sidebar after deleting all cookies because no data [Uns][[todo-mr][t1]]
  37. #1374686 [Firefox:General]-Lazily load LoginManagerContextMenu and SpellCheckHelper in nsContextMenu.js [Uns][]
  38. #1373718 [Firefox:Search]-Update follow-on search add-on to 0.9.1 - fix double reporting and fix case sensitivity [Uns][]
  39. #1374650 [Firefox:Theme]-Indenting of non-iconic subviewbutton items in the panels is wrong [Uns][[photon-structure]]
  40. #1374105 [Firefox:Theme]-Stop using the :not(:target) selector in chrome://browser/skin/customizableui/menu-arrow.svg [Uns][]
  41. #1374101 [Firefox:Theme]-Stop using the :not(:target) selector in sync-desktopIcon.svg and sync-mobileIcon.svg [Uns][]
  42. #1374099 [Firefox:Theme]-Stop using the :not(:target) selector in urlbar-star.svg and urlbar-tab.svg [Uns][]
  43. #1374474 [Firefox:Theme]-back button in 55 beta does not have greyed out disabled appearance in default theme [Uns][[photon-visual]]
  44. #1372954 [Firefox:Toolbars and Customization]-Sidebar button looks pressed/checked/hovered after restarting Firefox if sidebar was opened previously [Uns][[reserve-photon-structure]]
  45. #1362970 [Toolkit:Async Tooling]-Convert .then(null, ...) to .catch(...) [Uns][]
  46. #1286802 [Toolkit:Crash Reporting]-Add heap regions of the crash context to minidump (Windows) [Uns][]
  47. #1095426 [Toolkit:Places]-Convert JSON backups code to the new Bookmarks.jsm API [All][[reserve-photon-performance] [good next bug] [lang=js] [qf:p3]]
  48. #1355561 [Toolkit:Storage]-Add a new API to spinningly close the database when strictly needed, and ensure Close() does what it's named after [Uns][[fxsearch]]
  49. #1371945 [Toolkit:Storage]-Possible statement finalization crash on shutdown [Uns][[fxsearch]]
  50. #1369734 [Toolkit:Telemetry]-Improve aborted-session ping scheduling for reduced performance impact [Uns][[measurement:client][qf:p1]]
  51. #1374419 [Toolkit:Telemetry]-Make gHistograms constexpr to remove its initializer [Uns][]
  52. #1374108 [Toolkit:Themes]-Stop using the :not(:target) selector in the find bar's next/previous SVG icons [Uns][]
  53. #1374257 [Toolkit:XUL Widgets]-label-control_XBL_Constructor is visible on startup profiles [Uns][[photon-performance]]

    Partial Landings/Diagnostic Patches:
  1. #1373914 [Core:Audio/Video: Playback]-Crash in mozilla::MediaShutdownManager::Instance [Win][]
  2. #1365879 [Core:Graphics]-Merge Advanced Layers [Uns][keep-open]

    Beta 3 -> Beta 4 Changelog +1
  1. #1361008 [Core:Editor]-execCommand("defaultparagraphseparator", false, "p"); sometimes adds a surplus paragraph [Uns][]

Nightly 56 fixes since 20170613 (Gecko 55) ~522
Beta 55 fixes since 20170306 (Gecko 54) ~4988

Firefox 55 Beta 4 Testday
Nightly Blog
Release Calendar
Release Tracking
MozRegression Guide
Last edited by Josa on June 21st, 2017, 12:38 pm, edited 2 times in total.

alex_mayorga
 
Posts: 1864
Joined: May 8th, 2008, 9:35 am
Location: Monterrey/Zacatecas, Mexico

Post Posted June 20th, 2017, 8:33 am

¡Hola!

Image
Do others see this with the default theme?

Known bug?

¡Gracias!

Lurtz
 
Posts: 326
Joined: June 12th, 2016, 12:25 pm

Post Posted June 20th, 2017, 8:36 am

Yes, already fixed.

smsmith
Moderator

User avatar
 
Posts: 19719
Joined: December 7th, 2004, 8:51 pm
Location: Indiana

Post Posted June 20th, 2017, 8:55 am

alex_mayorga wrote:¡Hola!

Image
Do others see this with the default theme?

Known bug?

¡Gracias!

As a temporary workaround for today, you can use a lightweight theme or either of the compact themes.
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.

Sdar
 
Posts: 27
Joined: February 6th, 2012, 4:51 am

Post Posted June 20th, 2017, 9:44 am

The instruction at 0x00007FF8F4BEA5FF referenced memory at
0x00000000000000A0. The memory could not be read.

Some crashes probably addon related, but was working fine with the previous nightly.

Lurtz
 
Posts: 326
Joined: June 12th, 2016, 12:25 pm

Post Posted June 20th, 2017, 9:56 am

I'm hearing a lot about script not responding errors in Firefox 54.0 release right now. Did somebody break something?

WaltS48

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

Post Posted June 20th, 2017, 10:45 am

Firefox 55.0b3 has been officially released according to the Changelog, and just received the update.

Mozilla/5.0 (X11; Linux x86_64; rv:55.0) Gecko/20100101 Firefox/55.0 ID:20170619141703 CSet: be4a0ad5d6cab12fb89495d020532040b91be1f4
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

Peja Stija

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

Post Posted June 20th, 2017, 1:06 pm

Just FYI : Nice explanatory video on how to find the regression point if something broke in nightly.
https://www.youtube.com/watch?v=IwrWot3jVFI

avada
 
Posts: 1789
Joined: February 10th, 2008, 6:30 am
Location: Hungary

Post Posted June 20th, 2017, 1:12 pm

Peja Stija wrote:Just FYI : Nice explanatory video on how to find the regression point if something broke in nightly.
https://www.youtube.com/watch?v=IwrWot3jVFI

Does it also mention that it always identifies the wrong bug?

Peja Stija

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

Post Posted June 20th, 2017, 1:40 pm

avada wrote:
Peja Stija wrote:Just FYI : Nice explanatory video on how to find the regression point if something broke in nightly.
https://www.youtube.com/watch?v=IwrWot3jVFI

Does it also mention that it always identifies the wrong bug?

Really ? I personally haven't tried it yet, and unfortunately there's no issues section on their github page, how convenient. #-o

DN123ABC
 
Posts: 393
Joined: January 9th, 2017, 10:10 am

Post Posted June 20th, 2017, 2:18 pm

Well, I made the jump from Firefox 55.0b3 (32-bit) to 55.0b3 (64-bit). I downloaded the full installer, uninstalled the old one, and installed the new one in its place. Everything seems to work, except Flash, and I'm not sure, but it "feels" faster. It looks like it uses about the same memory resources as of right now. Extensions needed no intervention, though nothing got better, either.

On the Flash, here is what I got when I went to test it at https://helpx.adobe.com/shockwave/kb/sh ... ndows.html :

Windows with other browsers, such as Firefox, Google Chrome, or Opera To use Firefox or other (not Internet Explorer) browsers with Shockwave Player on your 64-bit system, do the following: Download the 32-bit version from the browser vendor's website. For example, Firefox is a 32-bit Web browser you can download from http://www.mozilla.org/firefox. While using the 32-bit version of your Web browser, go to: http://get.adobe.com/shockwave (the Shockwave Player Download Center). The download center installs Shockwave Player in your 32-bit Web browser. You are now ready to view content using Shockwave Player in your 32-bit browser. Note: Make sure you go to the Shockwave Player Download center in your 32-bit browser. If you try to go to the download center using a 64-bit Web browser, you will see a message from Adobe and a link back to this page, because you cannot install the current 32-bit Shockwave Player in your 64-bit Web browser.



All in all, aside from Flash breaking, it is OK. Nothing ground breaking. I guess I will just use Chrome or IE to look at pages with Flash going forward. I have not yet tried Shockwave.

avada
 
Posts: 1789
Joined: February 10th, 2008, 6:30 am
Location: Hungary

Post Posted June 20th, 2017, 3:42 pm

DN123ABC wrote:Well, I made the jump from Firefox 55.0b3 (32-bit) to 55.0b3 (64-bit). I downloaded the full installer, uninstalled the old one, and installed the new one in its place. Everything seems to work, except Flash, and I'm not sure, but it "feels" faster. It looks like it uses about the same memory resources as of right now. Extensions needed no intervention, though nothing got better, either.

On the Flash, here is what I got when I went to test it at https://helpx.adobe.com/shockwave/kb/sh ... ndows.html :

Windows with other browsers, such as Firefox, Google Chrome, or Opera To use Firefox or other (not Internet Explorer) browsers with Shockwave Player on your 64-bit system, do the following: Download the 32-bit version from the browser vendor's website. For example, Firefox is a 32-bit Web browser you can download from http://www.mozilla.org/firefox. While using the 32-bit version of your Web browser, go to: http://get.adobe.com/shockwave (the Shockwave Player Download Center). The download center installs Shockwave Player in your 32-bit Web browser. You are now ready to view content using Shockwave Player in your 32-bit browser. Note: Make sure you go to the Shockwave Player Download center in your 32-bit browser. If you try to go to the download center using a 64-bit Web browser, you will see a message from Adobe and a link back to this page, because you cannot install the current 32-bit Shockwave Player in your 64-bit Web browser.



All in all, aside from Flash breaking, it is OK. Nothing ground breaking. I guess I will just use Chrome or IE to look at pages with Flash going forward. I have not yet tried Shockwave.

A 64 bit version of flash is available for years now. Just install it: https://get.adobe.com/flashplayer/

James
Moderator

User avatar
 
Posts: 27328
Joined: June 18th, 2003, 3:07 pm
Location: Made in Canada

Post Posted June 20th, 2017, 7:02 pm

DN123ABC wrote:On the Flash, here is what I got when I went to test it at https://helpx.adobe.com/shockwave/kb/sh ... ndows.html :

All in all, aside from Flash breaking, it is OK. Nothing ground breaking. I guess I will just use Chrome or IE to look at pages with Flash going forward. I have not yet tried Shockwave.

Flash did not break just you trying to install the wrong Plugin as I replied at viewtopic.php?f=7&t=3031202&p=14753020#p14753020

megamanx
 
Posts: 105
Joined: April 6th, 2011, 8:35 am

Post Posted June 20th, 2017, 7:12 pm

I was thinking of asking them to optimize more for SwagBucks, that site can take a while to render, in comparison to Chromium builds. Only test I can suggest is searching multiple things. Pretty fast on my laptop with Opera. Of course my desktop is fast but you can noticeably see the difference in as well with both browsers. Clean Nightly/Firefox Stable/Firefox Beta build.

Rant: Many streaming sites are dragging on Firefox builds, mainly the CPU usage or optimizations, Chromium builds handle them nicely. Youtube chat during live streaming plays nice, but it didn't before, so I can tell optimizations are happening but the team can only look at the most known or sites they visit. (Using laptop as test: A6-6310, 4GB RAM, HDD, e10s on. Addon: ublock and last pass(also tested without add-ons))

I forgot the program they were recommending, and it wasn't MozRegressions.

Omega X

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

Post Posted June 20th, 2017, 7:53 pm

megamanx wrote:I forgot the program they were recommending, and it wasn't MozRegressions.


You're probably thinking about a stack tracer like AMD CodeAnalyst.

Or maybe you're looking for Gecko Profiler. Press SHIFT+CTRL+K and switch to the performance tab. [EDIT, forgot about the SHIFT part.]

MozRegressions is for finding regressions only. But the built in analyzer can tell you things about the performance you're seeing and can even save a replay file for devs to look at.
Last edited by Omega X on June 20th, 2017, 9:15 pm, edited 1 time in total.
Latest: Firefox/61.0.1 *ESR/60.1.0 - Mobile/61.0 - Thunderbird/52.9.1
Nightly: Nightly/63.0a1 - Mobile/63.0a1 - Daily/63.0a1

Return to Firefox Builds


Who is online

Users browsing this forum: No registered users and 5 guests