1526256 - Firefox nightly crashes on launch on Windows 10 aarch64

Status: RESOLVED DUPLICATE of bug 1525588

(Core :: General, defect)

Description

[Steven Noonan]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:65.0) Gecko/20100101 Firefox/65.0

Steps to reproduce:

• Run Windows 10 build 18317 (insider preview) on ARM64 device
• Launch current Firefox Nightly aarch64 Windows build

(Also I'm not sure where to get the nightly build ID without being able to launch Nightly and look at about:support, sorry)

Actual results:

Immediate crash on launch:

Faulting application name: firefox.exe, version: 67.0.0.6977, time stamp: 0x5c5cb2e0
Faulting module name: ntdll.dll, version: 10.0.18317.1000, time stamp: 0x637b341e
Exception code: 0xc0000409
Fault offset: 0x00000000000037b8
Faulting process id: 0x3734
Faulting application start time: 0x01d4bfa1171e7931
Faulting application path: C:\Program Files\Firefox Nightly\firefox.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 4e5e80fc-49f0-4de2-9feb-163b2630d28e
Faulting package full name:
Faulting package-relative application ID:

I updated, expecting that this build would fix the Nightly + FIDO U2F crash on the current Windows 10 insider build (see bug 1522077).

Expected results:

Firefox should run.

Comment 1

[Steven Noonan]

Also, is crash reporting broken on Windows aarch64? I never see the crash reporter, and I don't see any minidumps captured anywhere.

Comment 2

[Gingerbread Man]

This is probably a duplicate of bug 1526250.

(In reply to Steven Noonan from comment #1)

Also, is crash reporting broken on Windows aarch64? I never see the crash reporter, and I don't see any minidumps captured anywhere.

:gsvelto Considering bug 1513284, comment 23, I'm guessing the crash reporter is supposed to pop up. I'd also appreciate it if you'd triage this, since I see no obvious place for it.

Comment 3

[Gabriele Svelto [:gsvelto]]

The crash reporter is enabled but if the crash is happening very early during the startup process it might not have been set up yet. This seems like a very early crash so we might simply not be able to catch it.

Comment 4

[Steven Noonan]

:gsvelto On the earlier Nightly builds crashing with U2F it wasn't reporting either. And that was not early in the startup process.

Is there some way I can diagnose why the crash reporter isn't working?

Comment 5

[Gabriele Svelto [:gsvelto]]

Try browsing to about:crashparent. Firefox should crash and the crash reporter should come up immediately. If it doesn't then there's something broken about it.

Comment 7

[Steven Noonan]

Tried about:crashparent on build ID 20190204214259. No crash reporter. about:crashes is empty too.

Comment 8

[Steven Noonan]

Oops, didn't mean to re-open with that. I'll open a different bug report for the AWOL crash reporter.

Comment 9

[Berlin Tokyo]

This game are supported in your smart mobile and PC klondike solitaire card games so,now hurry up and let's play.