Open
Bug 1270666
Opened 9 years ago
Updated 2 years ago
Revisit handling of WM_*ENDSESSION
Categories
(Core :: Widget: Win32, defect, P3)
Tracking
()
NEW
Tracking | Status | |
---|---|---|
firefox49 | --- | affected |
People
(Reporter: bugzilla, Unassigned)
References
()
Details
(Whiteboard: tpi:+)
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•9 years 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.
Updated•8 years ago
|
Priority: -- → P1
Whiteboard: tpi:+
Comment 3•6 years ago
|
||
Moving to p3 because no activity for at least 1 year(s).
See https://github.com/mozilla/bug-handling/blob/master/policy/triage-bugzilla.md#how-do-you-triage for more information
Priority: P2 → P3
Comment 4•6 years ago
|
||
Moving to p3 because no activity for at least 1 year(s).
See https://github.com/mozilla/bug-handling/blob/master/policy/triage-bugzilla.md#how-do-you-triage for more information
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•