APPLICATION_HANG_BusyHang , NULL_POINTER_WRITE, Plugincontainer crashed with 0x80000003

UNCONFIRMED
Unassigned

Status

()

Core
Plug-ins
UNCONFIRMED
2 years ago
2 years ago

People

(Reporter: Robert Hartmann, Unassigned)

Tracking

50 Branch
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(3 attachments)

(Reporter)

Description

2 years ago
Created attachment 8818018 [details]
Firefox_plugin-container.exe_Crash.jpg

User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:50.0) Gecko/20100101 Firefox/50.0
Build ID: 20161129173726

Steps to reproduce:

Rebooting Windows 8.1 (64 bit) but didn't close Firefox 50.0.2 on my own, than crash.


Actual results:

While rebooting Windows 8.1 (64bit) , Firefox Gui closed and no crashreport was generated by crashreporter 
BUT 
plugin-container.exe (Plugin Container for Firefox)
Fileversion: 50.0.2.6177
Productversion: 50.0.2
Modificationdate: 01.12.2016 09:06
produced an "unknown software exception" (0x80000003) at 0x6d79ed43 
see attached screenshot (language is german)

Name 	Firefox
Version 	50.0.2
Build-ID 	20161129173726
Update-Kanal 	release
User-Agent 	Mozilla/5.0 (Windows NT 6.3; WOW64; rv:50.0) Gecko/20100101 Firefox/50.0
Betriebssystem 	Windows_NT 6.3






Expected results:

Firefox + plugin-container.exe should react conform on windows shutdown messages.
(Reporter)

Comment 1

2 years ago
Created attachment 8818019 [details]
firefox_50.0.2-Windbg-log_0544_2016-12-12_16-00-27-378.log

Running Firefox from Windbg.exe, storing logfile. 
Sending "Windows-Shutdown Signal" via rmtool.exe from "Microsoft Corporation\Logo Testing Tools for Windows" to log Firefox-behavior while recieving a shutdown-signal (or message) while Firefox is running via WinDbg.exe
(Reporter)

Comment 2

2 years ago
Created attachment 8818020 [details]
firefox_50.0.2_Send_shudown_first_only_to_plugincontainer-Windbg-log_0544_2016-12-12_16-27-08-902.log

Here I run FF inside Windbg but sending "Windows Shutdown signal (or message)" first to the plugin container and after that to Firefox
(Reporter)

Updated

2 years ago
See Also: → bug 1030586
(Reporter)

Updated

2 years ago
See Also: → bug 619036
(Reporter)

Updated

2 years ago
See Also: → bug 1203807

Updated

2 years ago
Component: Untriaged → Plug-ins
Product: Firefox → Core
(Reporter)

Updated

2 years ago
See Also: → bug 1309364
(Reporter)

Comment 3

2 years ago
There is a very old bugreport discussing information about 
handling  WM_QUERYENDSESSION & WM_ENDSESSION (and WM_CLOSE) 
from year 1999 : Bug 14807

just to mention newer requirements for Windows Vista and above
see following linked documents. 
From the last one can see that  "pre Vista" and "after Vista" has differend 
timing constraints to respect while handling WM_QUERYENDSESSION & WM_ENDSESSION. 


*  "Guidelines for Applications"
   ( https://msdn.microsoft.com/en-us/library/windows/desktop/aa373651(v=vs.85).aspx )
   Quote: Applications running on Windows Vista and Windows Server 2008
   should adhere to there guidelines to ensure that the Restart Manager
   can shut down and restart applications[...]


*  "Application Shutdown Changes in Windows Vista"
   ( https://msdn.microsoft.com/en-us/library/ms700677(v=vs.85).aspx )
   Quote: [...] In Windows Vista, if your application must block shutdown, in addition to returning
   FALSE or not responding to WM_QUERYENDSESSION, it should leverage this new UI by using a simple API
   to provide Windows with a reason string explaining why it is blocking shutdown. 
   This API is straightforward:
   BOOL ShutdownBlockReasonCreate(HWND hWnd, LPCWSTR pwszReason);
   BOOL ShutdownBlockReasonDestroy(HWND hWnd);
   BOOL ShutdownBlockReasonQuery(HWND hWnd, LPWSTR pwszBuff, DWORD *pcchBuff);

Because the ShutdownBlockReason-API is not available on older Windows I vote for using LoadLibrary + GetProcAddress for determine if these functions are available.
(Reporter)

Updated

2 years ago
See Also: → bug 14807
(In reply to Robert Hartmann from comment #3)
> just to mention newer requirements for Windows Vista and above

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