Crash using preferences / options

RESOLVED WORKSFORME

Status

defect
--
critical
RESOLVED WORKSFORME
11 months ago
11 months ago

People

(Reporter: wsmwk, Unassigned)

Tracking

({crash, regression})

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

11 months ago
+++ This bug was initially created as a clone of Bug #1460721 +++

With 2018-05-15 and 2018-05-18 nightly on windows 7 in new profile, the General options tab is shown but cicking other subdiaglogs/tabs is ineffective. Nightly 2018-05-08 works.  So I assume a regression of bug 1457021
(Reporter)

Comment 1

11 months ago
(Duplicate bug created from browswer and me both being stupid. So I'll just turn this one into the crash bug)

Seeing lots of crashes, and the graph at https://crash-stats.mozilla.com/crashes-per-day/?p=Thunderbird&v=62.0a1&v=60.0a1&v=61.0a1&v=62.0a1&hang_type=any&os=Windows&os=Mac+OS+X&os=Linux&date_start=2018-05-01&date_end=2018-05-19&submit=Generate shows 62.0a1 crash rate signficantly higher than previous versions starting around May 9.

Examples

bp-c132fb90-1f82-4966-891a-765ae0180515 "after crashing in the setup wizard twice I instead tried going to Preferences in Enigmail Nightly"

bp-afb99d92-00f4-4247-ac1e-1002a0180519 "Options are not working. repeatedly crashing. "
Severity: normal → critical
Keywords: crash
See Also: → 1462920
Summary: No Font list in Prefs > Display - TEST-UNEXPECTED-FAIL | /builds/worker/workspace/build/tests/mozmill/pref-window/test-font-chooser.js | test-font-chooser.js → Crash using preferences / options
(Reporter)

Comment 2

11 months ago
I seriously doubt it has anything to do with bug 1457021. The former crash dump has no usable stack, but the latter has some stack that has nothing to do with Fluent or L10n.

Also, notice that bug 1457021 is only moving JS of subdialogs which are browser specific.

Comment 4

11 months ago
Given that I closed bug 1462920, please check whether the crash is gone now.
Flags: needinfo?(vseerror)
(Reporter)

Comment 5

11 months ago
Crash rate of 62.0a1 is still about the same, i.e. much higher than 61.0a1. But there are lots of new crashes, enigmail recently fixed an options crash, and this crash reports containing FlsGetValue are gone (which is what I think this bug was about), so => WFM
Status: NEW → RESOLVED
Last Resolved: 11 months ago
Flags: needinfo?(vseerror)
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.