Closed Bug 1495010 Opened 6 years ago Closed 2 years ago

Closing Firefox after migration leads to a crash

Categories

(Firefox :: Migration, defect, P3)

All
Windows
defect

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox62 --- wontfix
firefox63 --- wontfix
firefox64 --- wontfix
firefox65 --- wontfix
firefox81 --- wontfix
firefox82 --- wontfix

People

(Reporter: emilghitta, Unassigned)

Details

(Keywords: crash, regression)

Crash Data

Attachments

(1 file)

Attached image migration.gif
This bug was filed from the Socorro interface and is
report bp-dcf0a23a-8c1e-49e9-8157-eb6b10180928.
=============================================================

Top 10 frames of crashing thread:

0 mozglue.dll mozalloc_abort memory/mozalloc/mozalloc_abort.cpp:35
1 xul.dll static void Abort xpcom/base/nsDebugImpl.cpp:471
2 xul.dll NS_DebugBreak xpcom/base/nsDebugImpl.cpp:453
3 xul.dll nsDebugImpl::Abort xpcom/base/nsDebugImpl.cpp:146
4 xul.dll XPTC__InvokebyIndex xpcom/reflect/xptcall/md/win32/xptcinvoke_asm_x86_64.asm:97
5  @0x1c93b4fdccf 
6 xul.dll XPCWrappedNative::CallMethod js/xpconnect/src/XPCWrappedNative.cpp:1233
7 xul.dll static bool XPC_WN_CallMethod js/xpconnect/src/XPCWrappedNativeJSOps.cpp:963
8 xul.dll js::InternalCallOrConstruct js/src/vm/Interpreter.cpp:553
9 xul.dll static bool InternalCall js/src/vm/Interpreter.cpp:607

=============================================================

[Steps to reproduce]:
1. Launch Firefox with ./firefox -no-remote -p -migration.
2. Import from Edge or Chrome.
3. Close Firefox.

[Expected results]:
Firefox successfully closes.

[Actual results]:
Several Firefox processes remain open and eventually, Firefox Crashes.

[Additional Information]:
For further information regarding this issue please observe the attached screencast.
Summary: Crash in AsyncShutdownTimeout | profile-change-teardown | Extension shutdown: formautofill@mozilla.org → Closing Firefox after migration leads to a crash
Keywords: regression
Not sure which Bug caused this regression. Had to find the regression manually.

Last good 2018-06-14
First bad 2018-06-15

Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=684094d78fb4&tochange=e51f8dbf0397
Matthew, could you have a look at this 63 regression? Is that something we can fix for 63?
Flags: needinfo?(MattN+bmo)
From crash-stats and the regression range I can see that this was also in 62.

Can you reproduce this using the normal user flow (not using the -migration command line argument) by moving your profiles.ini file aside?
Flags: needinfo?(emil.ghitta)
After discussing on Slack, I realized that we disabled the "no profiles.ini" case a year ago in bug 1403402.
Flags: needinfo?(emil.ghitta)
Just a note. This seems to be reproducible only by using the -migration command line argument. I didn't manage to reproduce this after importing via the "Import Now" button from homepage.
This feels like an edge case, if it requires the CL argument.
I agree that since this requires the command line argument it's not a high priority.
Flags: needinfo?(MattN+bmo)
Priority: -- → P3

Hello, did encounter the issue with Firefox not closing all it's processes after using the -migration option, but the crash never occurred, and the processes are still there, until I manually stop them in task manager. This was encountered on Firefox 82.0b8 under Windows 7.

Closing because no crashes reported for 12 weeks.

Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: