Closed Bug 1530026 Opened 7 years ago Closed 1 year ago

Crash reporter behind other windows

Categories

(Toolkit :: Crash Reporting, defect, P3)

Desktop
Windows 10
defect

Tracking

()

RESOLVED FIXED

People

(Reporter: overholt, Unassigned)

Details

If I trigger a parent process crash with about:crashparent, the resulting crash reporter application window is not top-most (i.e. other windows are on top of it). I'm not sure if this is ARM64-specific.

Seems similar to bug 1498433 but for Windows (or WoA?).

Confirmed to not be ARM64-specific.

No longer blocks: arm64-windows-bugs
Hardware: ARM64 → Desktop
Priority: -- → P3
Severity: normal → S3

Can we perhaps try this again with the new crash reporter client? I think this is likely fixed. I have only seen it placed as the top-most window on all platforms.

Andrew, does this still reproduce?

Flags: needinfo?(overholt)

(In reply to Gian-Carlo Pascutto [:gcp] from comment #3)

Andrew, does this still reproduce?

I was able to verify that with 128.0.3 it does not reproduce (granted, it's now Windows 11 but the same hardware). Thanks!

One minor nit: the crash reporter text looks a bit blurry like it's the wrong DPI or something.

Flags: needinfo?(overholt)

Marking this as fixed. IIRC we don't have full hi-DPI support just yet, that'd be bug 1521450.

Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED

WRT DPI, I did follow all guidance from Windows docs in the latest iteration of the crash reporter client, however "it's complicated" and I suspect those docs might be missing newer details.

You need to log in before you can comment on or make changes to this bug.