Open Bug 1660180 Opened 9 months ago Updated 8 months ago

Firefox is not opened after clicking Restart Firefox from the crash reporter while being unpacked in a Unicode folder

Categories

(Toolkit :: Crash Reporting, defect)

Desktop
All
defect

Tracking

()

Tracking Status
firefox-esr78 --- wontfix
firefox79 --- wontfix
firefox80 --- wontfix
firefox81 --- wontfix
firefox82 --- wontfix
firefox83 --- fix-optional

People

(Reporter: atrif, Unassigned)

Details

(Keywords: regression)

Attachments

(1 file)

Attached image crashparent.gif

Affected versions

  • 81.0a1 (20200819212829)
  • 80.0RC2 (20200818235255)
  • 79.0 (20200720193547)
  • 78.2.0esr (20200817153328)

Affected platforms

  • Windows 7x64

Steps to reproduce

  1. Install/unpack Firefox in a folder with Unicode characters (e.g ΏЉۺӜखगघ).
  2. Open Firefox and type about:crashparent.
  3. Click Restart Firefox from the crash reporter.

Expected result

  • Clicking Restart Firefox opens the browser.

Actual result

  • Win7: Nothing happens after clicking Restart Firefox from the crash reporter.
  • Ubuntu 18.04: Crash reporter is not displayed.
  • macOS 10.12: Crash reporter is not shown but Firefox quit unexpectedly window is displayed and clicking Reopen button opens Firefox again.

Regression range

  • Firefox 69.0.1(20190917135527) is also affected. I will search for one ASAP if there is one.

Notes

  • Attached a screen recording.
  • I cannot reproduce any of the issues above on Windows 10x64.

Suggested Severity: S3

Has Regression Range: --- → no
Has STR: --- → yes

Thanks for filing this. We set the path of the Firefox application in some environment variables for the crash reporter to read IIRC; there's plenty of chances to mess it up in cross-platform code so that's probably what's happening. The fact that it doesn't happen on Windows 10 might be due to the improved UTF-8 support on that platform.

Severity: -- → S3
QA Whiteboard: [qa-regression-triage]

Hello! After searching for a manual regression range I found these pushlogs:
Last good build: 750e71a8f79b3b745a6653e555e60acb122f1241
First bad build: e088bb62f286425a30a925fc3355eb40c92f79c1
Pushlog: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=750e71a8f79b3b745a6653e555e60acb122f1241&tochange=e088bb62f286425a30a925fc3355eb40c92f79c1

I don't know for sure that the above pushlog is correct due to the few bugs(and android related) so I'm adding a second wider one containing the changes from 2018-09-14 to 2018-09-15:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=28baa3df5f0f530faee1900f43c463f6b77b985c&tochange=5d14d1e9f74d7cac00bdefbda29244d586645682

This changelog contains bug 1490605 with UTF-8 changes so maybe it can be the regressor. If anything else is needed please let me know. Thanks!

Has Regression Range: no → yes
You need to log in before you can comment on or make changes to this bug.