If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Revisit handling of WM_*ENDSESSION

NEW
Unassigned

Status

()

Core
Widget: Win32
P2
normal
a year ago
a month ago

People

(Reporter: aklotz, Unassigned)

Tracking

Trunk
Unspecified
Windows
Points:
---

Firefox Tracking Flags

(firefox49 affected)

Details

(Whiteboard: tpi:+, URL)

We should review the contents of the MSDN document "Application Shutdown Changes in Windows Vista" (see URL) and consider updating our code with ShutdownBlockReasonCreate and friends.

Yes, the real problem is god-awful shutdown times, but I have seen reports from users in the wild who are seeing "Well, this is embarrassing" messages when starting Firefox due to forced process termination during a previous Windows shutdown.

At least presenting the user with some additional info could help them make an informed decision as to whether or not they should wait.

Comment 1

a year ago
I see this all the time on my Surface book.

We also continue to have problems where we spin the Windows event loop after receiving WM_ENDSESSION, which just kills the process outright. You're not allowed to do that AIUI.
Priority: -- → P1
Whiteboard: tpi:+
Benjamin, moving to p2 per your request in email.
Priority: P1 → P2
You need to log in before you can comment on or make changes to this bug.