The first official 20171004 builds are out

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

The first official 20171004 builds are out

Post by Josa »

Previous Nightly Builds thread 20171003

The first official 20171004 NIGHTLY builds are out
.The Official Firefox 57 Beta 6 builds are not yet out

Previous NIGHTLY: 20171003 (Fx 58.0a1)
Previous BETA: 20171003 (Fx 57.0b5)

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


Fixed:
  1. NIGHTLY +71
  2. #1405009
  3. #1405139 [Core:Audio/Video: Playback]-fsanitize=enum (ubsan) runtime errors for TrackInfo::TrackType [Uns][[tor]]
  4. #1405258 [Core:Audio/Video: cubeb]-Update libcubeb to revision ba2a89611875cd9f2dabae99a362461b03c0dd3d [Uns][]
  5. #1405162 [Core:DOM: Core & HTML]-Fix CC Macros for HTMLOutputElement [Uns][]
  6. #1070763 [Core:DOM: Core & HTML]-XHR does not sniff the BOM before decoding responseText [All][[lang=c++]]
  7. #1403055 [Core:DOM: Events]-[Pointer Event] Revise the implementation to fire boundary events by handling pointercancel and pointerup [Uns][]
  8. #1405439 [Core:DOM]-Cannot cast nullptr to boolean in VR [Uns][[tor]]
  9. #1319342 [Core:DOM]-Cloning a node runs concept-create-element steps with synchronous-custom-elements-flag unset which enqueues an upgrade reaction [Uns][dom-ce-m2]
  10. #1405348 [Core:DOM]-eliminate extraneous AddRef when moving nsIdentifierMapEntry [All][]
  11. #1405353 [Core:DOM]-stop using nsAutoPtr in nsGlobalWindow [All][]
  12. #1393600 [Core:Disability Access APIs]-Handler <--> Proxy Interface Mismatch [Win][]
  13. #1402951 [Core:Disability Access APIs]-no show events for content on document load complete [Uns][]
  14. #1403915 [Core:Graphics: WebRender]-Delete all the layers-full WR code [Uns][[wr-mvp] [gfx-noted]]
  15. #1404782 [Core:Graphics: WebRender]-Do not mutate display list in the layers-free mode [Uns][[wr-mvp]]
  16. #1404091 [Core:Graphics: WebRender]-Re-enable layout/reftests/bugs/593243-1.html (aka fix invalidation detection in WebRenderLayerManager) [Uns][[wr-mvp] [gfx-noted]]
  17. #1403971 [Core:Graphics: WebRender]-Update webrender to aa81aebba2c1b8ff8af5d40796154d66349fd131 [Uns][[gfx-noted]]
  18. #1404955 [Core:Graphics: WebRender]-Use ComplexClipRegion instead of WrComplexClipRegion [Uns][[wr-mvp]]
  19. #1405417 [Core:IPC]-Ambiguous typename in ipc/mscom/PassthruProxy.h [Uns][[tor]]
  20. #1404226 [Core:IPC]-fsanitize=enum (ubsan) runtime errors for mozilla::ipc::Transport::Mode [Uns][[tor]]
  21. #1402057 [Core:ImageLib]-Update in-tree libpng to version 1.6.34 [All][[gfx-noted]]
  22. #1360211 [Core:JavaScript Engine: JIT]-Merge WasmActivation into JitActivation [Uns][]
  23. #1405122 [Core:JavaScript Engine: JIT]-Use variadic templates for MixPolicy [Uns][]
  24. #1405156 [Core:JavaScript Engine: JIT]-fsanitize=enum (ubsan) runtime error for js::jit::ABIArgType [Uns][[tor]]
  25. #1404787 [Core:JavaScript Engine]-Change some symbols to public in SpiderMonkey shared library [Uns][]
  26. #1404395 [Core:JavaScript Engine]-Simplify PreliminaryObjectArrayWithTemplate::maybeAnalyze [All][]
  27. #1404859 [Core:JavaScript Engine]-Simplify dead object proxy state tracking [Uns][]
  28. #1403911 [Core:JavaScript Engine]-Various clean-ups for jsstr.h/cpp [Uns][]
  29. #1405154 [Core:JavaScript Engine]-fsanitize=enum (ubsan) runtime error for JSExnType [Uns][[tor]]
  30. #1405016 [Core:JavaScript: GC]-Include full/zone GC information in JS_GC_PROFILE output [Uns][]
  31. #1405015 [Core:JavaScript: Internationalization API]-formatToParts shouldn't get the legacy unwrapping behaviour [Uns][]
  32. #1405121 [Core:JavaScript: Standard Library]-Add a fast path for native objects to TestIntegrityLevel [Uns][]
  33. #1405123 [Core:JavaScript: Standard Library]-Only create the outer wrapper object in JSON.stringify when necessary [Uns][]
  34. #1404179 [Core:Layout]-Intermittent css-ruby/line-breaking-1.html == css-ruby/line-breaking-1-ref.html | image comparison, max difference: 255, number of differing pixels: 252 [Uns][[stockwell fixed:product]]
  35. #1402766 [Core:Layout]-stylo: crash near null [@ nsInlineFrame::UpdateStyleOfOwnedAnonBoxesForIBSplit] [Uns][]
  36. #1405159 [Core:Memory Allocator]-Consider asserting against freeing incorrectly offset pointers [Uns][]
  37. #1401224 [Core:Networking: Cache]-Assertion failure: aLength > 0 (Writing a zero-sized chunk), at image/SourceBuffer.cpp:348 [Uns][]
  38. #1403010 [Core:Networking: Cache]-Intermittent toolkit/components/aboutmemory/tests/test_memoryReporters.xul | application crashed [@ arena_salloc] [Uns][]
  39. #1399590 [Core:Networking: Cookies]-Intermittent PROCESS-CRASH | Main app process exited normally | application crashed [@ nsPermissionManager::CommonTestPermissionInternal(nsIPrincipal *,nsIURI *,char const *,unsigned int *,bool,bool)] after Assertion: PermissionAvaliable(prin, a [Uns][]
  40. #1405312 [Core:Plug-ins]-Remove dead code in plugin host [Uns][]
  41. #1382323 [Core:Security: Process Sandboxing]-Firefox 54 on Fedora 26 doesn't launch custom protocol handler [Lin][sb+]
  42. #1380674 [Core:Security: Process Sandboxing]-[mac] remove the ability to create directories in the temp directory [Mac][sb+]
  43. #1400407 [Core:WebVR]-Cleanup WebVR Dead Code [Uns][]
  44. #1402272 [Firefox:Address Bar]-Evaluate a different approach for adjustSiteIconStart [Uns][[fxsearch]]
  45. #1404674 [Firefox:Address Bar]-Focus doesn't move to content after clicking Home button with custom web page [Win][]
  46. #1404138 [Firefox:Developer Tools: Console]-New web console http inspection completely broken [Uns][]
  47. #1403065 [Firefox:Developer Tools: Console]-Object actor's enumProperties assume incorrect things about length property [Uns][[reserve-console-html]]
  48. #1403244 [Firefox:Developer Tools: Console]-Repeat bubble grows with the body of the message [Uns][[reserve-console-html]]
  49. #1405063 [Firefox:Developer Tools: Framework]-Adding a tab in the TabBar should be able to take an index to specify where to add the tab [Uns][]
  50. #1402397 [Firefox:Developer Tools: Framework]-CamelCase all React component files in \devtools\client\webconsole\new-console-output\components\ [Uns][]
  51. #1383037 [Firefox:Developer Tools: Framework]-Use only one debounce function in DevTools [Uns][]
  52. #1398722 [Firefox:Developer Tools: Inspector]-"Edit position" button disappears after modifying the offset of an element [Uns][]
  53. #1382171 [Firefox:Developer Tools: Inspector]-Remove MDN Docs widget [Uns][]
  54. #1400297 [Firefox:Developer Tools: JSON Viewer]-Too low contrast for netInfoHeadersGroup in JSON Viewer [Uns][]
  55. #1403389 [Firefox:Developer Tools: Shared Components]-Some devtools splitters use cursors with a single arrow instead of a double arrow [Uns][]
  56. #1401946 [Firefox:General]-Show profile path in about:support [Uns][]
  57. #1405438 [Firefox:Installer]-Stub installer exit code never initialized if exited from profile cleanup prompt [Win][]
  58. #1389721 [Firefox:Pocket]-Right-click > Save Link to Pocket doesn't work [Uns][[reserve-photon-structure]]
  59. #1379210 [Firefox:Preferences]-Layout issue with Learn more link for "Use Tracking Protection to block known trackers" [Uns][[photon-preference]]
  60. #1405237 [Firefox:Preferences]-Revert unexpected npm-shrinkwrap.json changes in bug 1349689 [Uns][[photon-preference]]
  61. #1404078 [Firefox:Screenshots]-Add full page cutoff warning to Screenshots [Uns][]
  62. #1403665 [Firefox:Screenshots]-Exclude " and ? from download filenames [Uns][]
  63. #1403052 [Firefox:Sync]-tabs collection may exceed memcached server limits [Uns][]
  64. #1404465 [Firefox:Tabbed Browser]-Add back `browser.tabs.tabMinWidth` and set the default width to 50 [Uns][]
  65. #1389784 [Firefox:Tabbed Browser]-Firefox 57 regression: ghost tabs (can't select the browser, get errors implying there's no browser hooked up to the tab) [Mac][]
  66. #1404497 [Firefox:Theme]-Consider not hiding photon grab space when maximized because it is inconsistent with Edge [Uns][[reserve-photon-visual]]
  67. #1402929 [Firefox:Toolbars and Customization]-Clearer labeling of overflow panel and its dropzone targets in customize mode [Uns][[reserve-photon-structure]]
  68. #1403382 [Firefox:Toolbars and Customization]-Dragging the back button out of the toolbar in customize mode adjusts the toolbar height [Uns][[reserve-photon-structure]]
  69. #1403585 [Toolkit:Telemetry]-URL hash for subsections fails in about:telemetry [All][[good next bug][lang=js]]
  70. #1404746 [Toolkit:WebExtensions: Compatibility]-Ignore minimum_opera_version in WebExtensions manifest [Uns][]
  71. #1395074 [Toolkit:WebExtensions: Frontend]-Icon badge isn't cleared when a new page is loaded [Uns][]
  72. #1397611 [Toolkit:WebExtensions: General]-Allow Web Extensions to control privacy.resistFingerprinting [Uns][[fingerprinting]]
  1. Partial Landings/Diagnostic Patches:
  2. #1403397 [Core:CSS Parsing and Computation]-stylo: Land Nightly diagnostic code to mprotect stylist hashtables outside of rebuilds in order to determine what's corrupting them [Uns][]
  3. #651120 [Core:DOM: Core & HTML]-Remove DOM node child array storage [All][[qf:p2]]
  1. Beta 5 -> Beta 6 Changelog +7
  2. #1321960 [Core:Disability Access APIs]-Browser becomes hangs up and Windows becomes almost unusable(all app becomes too slow. keyin slow).. [Uns][]
  3. #1402377 [Core:WebRTC: Audio/Video]-Mic goes silent after unplugging (different device) camera (regression) [Mac][]
  4. #1400920 [Firefox:Activity Streams: Newtab]-The pocket section briefly shows up and causes the scrollbar to make the whole page flicker [Uns][]
  5. #1403215 [Firefox:Activity Streams: Newtab]-Fix broken Snippets pref, perceived performance and bug fixes to Activity Stream [Uns][]
  6. #1404345 [Firefox:Activity Streams: Newtab]-Users are upset and confused about how to turn off Pocket or other sections [Uns][]
  7. #1366405 [Firefox:Theme]-We're forcing the window's main layer to be transparent on Windows 10 because we think it has a glass effect [Uns][[reserve-photon-visual]]
  8. #1395674 [Firefox:Theme]-[Photon] Inconsistent appearance of sliding subviews in the overflow menu [Uns][[reserve-photon-structure]]

Nightly 58 fixes since 20170921 (Gecko 57) ~720
Beta 57 fixes since 20170802 (Gecko 56) ~3257

Nightly Blog
Release Calendar
Release Tracking
MozRegression Guide
Last edited by Josa on October 5th, 2017, 7:13 am, edited 1 time in total.
Lurtz
Posts: 359
Joined: June 12th, 2016, 12:25 pm

Re: The first official 20171004 builds are not yet out

Post by Lurtz »

About OMTP: Strangely I've seen more white, unrendered areas with it enabled than without. Don't know if that's expected or not.

Performance sheriffing announced the following improvements:
39% tsvgr_opacity summary windows7-32 opt e10s 435.66 -> 265.49
26% tsvgr_opacity summary windows10-64 opt e10s 290.31 -> 215.46
19% tsvgr_opacity summary windows10-64 pgo e10s 256.81 -> 206.84
12% tsvgx summary windows7-32 opt e10s 523.38 -> 461.34
11% tsvgx summary windows10-64 opt e10s 265.15 -> 235.37
User avatar
Omega X
Posts: 8225
Joined: October 18th, 2007, 2:38 pm
Location: A Parallel Dimension...

Re: The first official 20171004 builds are not yet out

Post by Omega X »

Lurtz wrote:About OMTP: Strangely I've seen more white, unrendered areas with it enabled than without. Don't know if that's expected or not.
I've seen that too, but only when I scroll upward on some websites.
Lurtz
Posts: 359
Joined: June 12th, 2016, 12:25 pm

Re: The first official 20171004 builds are not yet out

Post by Lurtz »

Upward sounds right. Do you know if there's a ticket? I only have anecdotical evidence, nothing to reproduce...
User avatar
Omega X
Posts: 8225
Joined: October 18th, 2007, 2:38 pm
Location: A Parallel Dimension...

Re: The first official 20171004 builds are not yet out

Post by Omega X »

Lurtz wrote:Upward sounds right. Do you know if there's a ticket? I only have anecdotical evidence, nothing to reproduce...
I've seen old OMTP bugs on the matter but none on the new version of it.
https://bugzilla.mozilla.org/show_bug.cgi?id=1369541

EDIT: I've also caught an awesome Gecko Profile with super long event processing delays.
User avatar
streetwolf
Posts: 2706
Joined: August 21st, 2011, 8:07 am
Location: NJ (USA)

Re: The first official 20171004 builds are not yet out

Post by streetwolf »

Webrender is getting better everyday. I'm on then latest inbound and besides the white screen when starting Fx most sites work nicely. Wikipedia on the other hand has some jerkiness when scrolling as I'm sure other sites do too.
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
User avatar
Grantius
Posts: 1545
Joined: June 28th, 2011, 4:14 pm
Contact:

Re: The first official 20171004 builds are not yet out

Post by Grantius »

streetwolf wrote:Webrender is getting better everyday. I'm on then latest inbound and besides the white screen when starting Fx most sites work nicely. Wikipedia on the other hand has some jerkiness when scrolling as I'm sure other sites do too.
What's the RAM usage like? Last time I tried it, it was very heavy on RAM.
Micro gaming box: AMD A10-7800 APU, 8gb RAM M350 ITX case (size of a book), Windows 10/Ubuntu
Tablet/Laptop: Asus Transformer T100, Intel Atom 2GB RAM, Windows 10 x86
Mobile:Xiaomi Redmi Note 3 Pro
ashleylai87
Posts: 218
Joined: December 13th, 2013, 7:40 pm

Re: The first official 20171004 builds are not yet out

Post by ashleylai87 »

I just wish mozilla fixes the bug with deleting history from urlbar....
Going to CTRL+H to delete certain history is too problematic....
Lurtz
Posts: 359
Joined: June 12th, 2016, 12:25 pm

Re: The first official 20171004 builds are not yet out

Post by Lurtz »

Omega X wrote:I've seen old OMTP bugs on the matter but none on the new version of it.
https://bugzilla.mozilla.org/show_bug.cgi?id=1369541

EDIT: I've also caught an awesome Gecko Profile with super long event processing delays.
Here's a ticket: https://bugzilla.mozilla.org/show_bug.cgi?id=1405589
User avatar
Omega X
Posts: 8225
Joined: October 18th, 2007, 2:38 pm
Location: A Parallel Dimension...

Re: The first official 20171004 builds are not yet out

Post by Omega X »

Lurtz wrote:
Omega X wrote:I've seen old OMTP bugs on the matter but none on the new version of it.
https://bugzilla.mozilla.org/show_bug.cgi?id=1369541

EDIT: I've also caught an awesome Gecko Profile with super long event processing delays.
Here's a ticket: https://bugzilla.mozilla.org/show_bug.cgi?id=1405589
I just filed that. :mrgreen:

Grantius wrote:
streetwolf wrote:Webrender is getting better everyday. I'm on then latest inbound and besides the white screen when starting Fx most sites work nicely. Wikipedia on the other hand has some jerkiness when scrolling as I'm sure other sites do too.
What's the RAM usage like? Last time I tried it, it was very heavy on RAM.
I think that was the bug where it wasn't evicting the memory at all. It just stacked until a crash happened.
TheVisitor
Posts: 5472
Joined: May 13th, 2012, 10:43 am

Re: The first official 20171004 builds are not yet out

Post by TheVisitor »

Latest hourly m-c win32 build has changed something in the tab-strip. Have not investigated deeply yet but the tabs are shrinking down to a very small horizontal size putting 25 tabs on the strip 'without' a scroll. This change will hit today's Nightly.

EDIT: looks like its probably bug https://bugzilla.mozilla.org/show_bug.cgi?id=1404465
Add browser.tabs.tabMinWidth to control minimum tab width, and set to 50 by default (looks like from the patch the original min was 100)

Pref to control width in about:config browser.tabs.tabMinWidth

Looks like more 'Chromification' to me...

I now have 26 tabs open and the 'Active' tab only shows the Favicon and the close button. Way too narrow, I suspect there will be lots of negative feedback on this one.
Lurtz
Posts: 359
Joined: June 12th, 2016, 12:25 pm

Re: The first official 20171004 builds are not yet out

Post by Lurtz »

That's horrible. One of the reasons Chrome can never be my main browser is the unusable tab strip.

I really hope they keep this optional or I don't know what I'll do.

Edit: After reading the ticket it mostly sounds like a migration option for Chrome users (and maybe the new standard setting), but keeping the option alive, probably even in about:preferences.
Last edited by Lurtz on October 4th, 2017, 5:32 am, edited 1 time in total.
User avatar
GHM113
Posts: 707
Joined: December 16th, 2015, 3:59 am
Location: Moscow, Russia

Re: The first official 20171004 builds are not yet out

Post by GHM113 »

TheVisitor wrote:Latest hourly m-c win32 build has changed something in the tab-strip. Have not investigated deeply yet but the tabs are shrinking down to a very small horizontal size putting 25 tabs on the strip 'without' a scroll. This change will hit today's Nightly
Mozilla should implement multirow tab bar, simple and elegant solution.
Sorry for my poor English.
Lurtz
Posts: 359
Joined: June 12th, 2016, 12:25 pm

Re: The first official 20171004 builds are not yet out

Post by Lurtz »

From the ticket:
I believe UX thinks that tab scrolling is a pretty confusing UI affordance, and that if we can avoid it, we should.

](*,) ](*,) ](*,)

What's more confusing about a scroll option than having tiny tabs where only icons can be read? This isn't even the case on mobile, there I'm getting a full tab overview in Chrome no matter how many tabs are open.
User avatar
sciguyryan
Folder@Home
Posts: 2181
Joined: November 10th, 2004, 1:33 pm
Location: Wales

Re: The first official 20171004 builds are not yet out

Post by sciguyryan »

TheVisitor wrote:Latest hourly m-c win32 build has changed something in the tab-strip. Have not investigated deeply yet but the tabs are shrinking down to a very small horizontal size putting 25 tabs on the strip 'without' a scroll. This change will hit today's Nightly.

EDIT: looks like its probably bug https://bugzilla.mozilla.org/show_bug.cgi?id=1404465
Add browser.tabs.tabMinWidth to control minimum tab width, and set to 50 by default (looks like from the patch the original min was 100)

Pref to control width in about:config browser.tabs.tabMinWidth

Looks like more 'Chromification' to me...

I now have 26 tabs open and the 'Active' tab only shows the Favicon and the close button. Way too narrow, I suspect there will be lots of negative feedback on this one.
Nice find, that was pretty ugly. I'm glad it was easy to revert at least.
Cheers!

Ryan Jones
Locked