Summary: | www/waterfox 56.2.0.31_5 fails to start at the tail of a refresh routine – TelemetryEnvironment.jsm, line 502 | ||||||
---|---|---|---|---|---|---|---|
Product: | Ports & Packages | Reporter: | Graham Perrin <grahamperrin> | ||||
Component: | Individual Port(s) | Assignee: | Jan Beich <jbeich> | ||||
Status: | Closed Not Accepted | ||||||
Severity: | Affects Only Me | CC: | grahamperrin | ||||
Priority: | --- | Flags: | bugzilla:
maintainer-feedback?
(jbeich) |
||||
Version: | Latest | ||||||
Hardware: | Any | ||||||
OS: | Any | ||||||
URL: | https://github.com/MrAlex94/Waterfox/blob/9b3413e76ae10c9af5bb1401af8c39c64e7d04aa/toolkit/components/telemetry/TelemetryEnvironment.jsm#L502 | ||||||
Attachments: |
|
Description
Graham Perrin
2018-06-11 19:42:56 UTC
https://redd.it/8qcg7r – invitation to test on other platforms. > $ waterfox --safe-mode -p maf
If you don't provide details about "maf" profile warnings aren't enough. Can you attach compressed (and sanitized for privacy) profile directory for me to try to reproduce?
waterfox-56.2.0.31_5 doesn't crash here on 10.4 i386 and 12.0 amd64.
$ waterfox --safe-mode --new-instance --profile $(mktemp -d)
1528747441978 addons.xpi WARN Error parsing extensions state: [Exception... "Component returned failure
code: 0x80520012 (NS_ERROR_FILE_NOT_FOUND) [amIAddonManagerStartup.readStartupData]" nsresult: "0x80520012 (NS_ERROR_FILE_NOT_FOUND)" location: "JS frame :: resource://gre/modules/addons/XPIProvider.jsm :: loadExtensionState :: line 1554" data: no] Stack trace: loadExtensionState()@resource://gre/modules/addons/XPIProvider.jsm:1554 < getInstallState()@resource://gre/modules/addons/XPIProvider.jsm:1589 < checkForChanges()@resource://gre/modules/addons/XPIProvider.jsm:3109 < startup()@resource://gre/modules/addons/XPIProvider.jsm:2188 < callProvider()@resource://gre/modules/AddonManager.jsm:269 < _startProvider()@resource://gre/modules/AddonManager.jsm:739 < startup()@resource://gre/modules/AddonManager.jsm:906 < startup()@resource://gre/modules/AddonManager.jsm:3090 < observe()@jar:file:///usr/local/lib/waterfox/omni.ja!/components/addonManager.js:65
###!!! [Child][MessageChannel] Error: (msgtype=0x620001,name=PRemoteSpellcheckEngine::Msg___delete__) Channel closing: too late to send/recv, messages will be lost
Both of the above warnings are innocuous:
- on fresh profiles there's no state for addon manager to restore
- child processes race on shutdown
Sorry for the lack of detail. I whittled it down to a single-extension case (there may be others): Mozilla Archive Format <https://addons.mozilla.org/addon/mozilla-archive-format/> Here, I seem to also get a crash after simply accepting the invitation to restart following installation of the extension. (I normally ignore those invitations – prefer to quit then start (not restart).) I'll attach a profile. Maybe relevant: Mozilla Archive Format is truly incompatible with multi-process, and (with 56.0.3 IIRC) Waterfox lost the ability to automatically disable multi-process when such extensions are enabled. I wondered whether another reportedly incompatible extension would have a similar effect. Tested briefly with InfoLister <https://addons.mozilla.org/addon/infolister/> alone in a new profile, I could not reproduce a bug. ---- > Not reproducible with general release 56.2.0 on a Mac. I just realised, multiprocess windows are 'Disabled forcibly' with this release of Waterfox on Mac OS X 10.9.5. Created attachment 194186 [details] profile > … compressed (and sanitized for privacy) profile directory for me to try to reproduce? Not sanitised (this was a 'new' profile with, if I recall correctly, just one extension). Thanks Not FreeBSD-specific, reproducible on Linux so I raised issues in the main Waterfox repo: e10s: crash (failure to restart) after installing an incompatible extension · Issue #616 · MrAlex94/Waterfox <https://github.com/MrAlex94/Waterfox/issues/616> e10s: crash (failure to start) when attempting to refresh with an incompatible extension enabled · Issue #617 … <https://github.com/MrAlex94/Waterfox/issues/617> Rejecting; this bug 228903 is effectively a duplicate of those two. ---- Sorry for the wasted space here. Prior to reporting, I had a _terribly_ confusing few hours, complicated by (amongst other things) Add-on Compatibility Reporter no longer working as expected – providing false reports of compatibility <https://redd.it/8qd0xe>. |