Firefox hangs whenever a file save/open dialogue is to be opened
I have Firefox 3.6.12 (but this problem started since 3.4 I think). It normally works fine and I have no problem with any website or add-on in particular. However, anytime I have to download a file or open a file (e.g. when using SQLite Manager add-on) then the file dialogue never appears and at this point Firefox becomes unresponsive with the hour-glass symbol being displayed. I have submitted crash reports (after forcing Firefox to close) and have also looked at ProcessExplorer stack trace - a sample of which is below:
ntkrnlpa.exe!NtInitialUserProcessBuffer+0x7b ntkrnlpa.exe!MiAddWorkingSetPage+0x174 ntkrnlpa.exe!MiAddWsleHash+0x12a ntkrnlpa.exe!PopDispatchFullWake+0x9a ntkrnlpa.exe!KiInterruptTemplate+0x62 ntdll.dll!KiFastSystemCallRet ntdll.dll!ZwWaitForSingleObject+0xc kernel32.dll!WaitForSingleObjectEx+0xa8 kernel32.dll!WaitForSingleObject+0x12 nspr4.dll!PR_MD_WAIT_CV+0xc9 nspr4.dll!PR_GetPrimordialCPU+0x78 nspr4.dll!PR_WaitCondVar+0x3b xul.dll!NS_StringContainerInit_P+0x107 nspr4.dll!PRP_TryLock+0x989 nspr4.dll!PR_Now+0xf5d MOZCRT19.dll!endthreadex+0x106
ntkrnlpa.exe!NtInitialUserProcessBuffer+0x7b
ntkrnlpa.exe!MiAddWorkingSetPage+0x174
ntkrnlpa.exe!MiAddWsleHash+0x12a
ntkrnlpa.exe!PopDispatchFullWake+0x9a
ntkrnlpa.exe!KiInterruptTemplate+0x62
ntdll.dll!KiFastSystemCallRet
ntdll.dll!ZwWaitForSingleObject+0xc
kernel32.dll!WaitForSingleObjectEx+0xa8
kernel32.dll!WaitForSingleObject+0x12
nspr4.dll!PR_MD_WAIT_CV+0xc9
nspr4.dll!PR_GetPrimordialCPU+0x78
nspr4.dll!PR_WaitCondVar+0x3b
xul.dll!gfxSkipChars::BuildShortcuts+0x1bdb
xul.dll!gfxFontGroup::FindFontForChar+0x550
xul.dll!gfxWindowsSurface::gfxWindowsSurface+0x264
xul.dll!XRE_main+0x9554
nspr4.dll!PRP_TryLock+0x989
nspr4.dll!PR_Now+0xf5d
MOZCRT19.dll!endthreadex+0x106
ntkrnlpa.exe!NtInitialUserProcessBuffer+0x7b
ntkrnlpa.exe!MiAddWorkingSetPage+0x174
ntkrnlpa.exe!MiAddWsleHash+0x12a
ntkrnlpa.exe!PopDispatchFullWake+0x9a
ntkrnlpa.exe!KiInterruptTemplate+0x62
ntdll.dll!KiFastSystemCallRet
ntdll.dll!ZwWaitForSingleObject+0xc
kernel32.dll!WaitForSingleObjectEx+0xa8
kernel32.dll!WaitForSingleObject+0x12
nspr4.dll!PR_MD_WAIT_CV+0xc9
nspr4.dll!PR_GetPrimordialCPU+0x78
nspr4.dll!PR_Wait+0x51
xul.dll!gfxASurface::GetDefaultContextFlags+0x4f
xul.dll!gfxFontGroup::FindFontForChar+0x74f
xul.dll!gfxWindowsSurface::gfxWindowsSurface+0x264
xul.dll!XRE_main+0x9554
nspr4.dll!PRP_TryLock+0x989
nspr4.dll!PR_Now+0xf5d
MOZCRT19.dll!endthreadex+0x106
ntkrnlpa.exe!NtInitialUserProcessBuffer+0x7b
ntkrnlpa.exe!MiAddWorkingSetPage+0x174
ntkrnlpa.exe!MiAddWsleHash+0x12a
win32k.sys!xxxSleepThread+0x192
win32k.sys!xxxInterSendMsgEx+0x7f6
win32k.sys!xxxSendMessageTimeout+0x11f
win32k.sys!xxxWrapSendMessage+0x1b
win32k.sys!NtUserMessageCall+0x8a
ntkrnlpa.exe!KiInterruptTemplate+0x62
ntdll.dll!KiFastSystemCallRet
USER32.dll!NtUserMessageCall+0xc
USER32.dll!SendMessageW+0x7f
ole32.dll!CDllHost::GetApartmentToken+0x1f7
ole32.dll!DoSTApartmentCreate+0x12
ole32.dll!CClassCache::GetActivatorFromDllHost+0xa3
ole32.dll!CClassCache::GetOrCreateApartment+0x20
ole32.dll!FindOrCreateApartment+0x46
ole32.dll!CProcessActivator::GetApartmentActivator+0xc7
ole32.dll!CProcessActivator::CCICallback+0x17
ole32.dll!CProcessActivator::AttemptActivation+0x2c
ole32.dll!CProcessActivator::ActivateByContext+0x42
ole32.dll!CProcessActivator::CreateInstance+0x49
ole32.dll!ActivationPropertiesIn::DelegateCreateInstance+0xf7
ole32.dll!CClientContextActivator::CreateInstance+0x8f
ole32.dll!ActivationPropertiesIn::DelegateCreateInstance+0xf7
ole32.dll!ICoCreateInstanceEx+0x3c9
ole32.dll!CComActivator::DoCreateInstance+0x28
ole32.dll!CoCreateInstanceEx+0x1e
ole32.dll!CoCreateInstance+0x37
SHLWAPI.dll!SHCoCreateInstanceAC+0x3a
SHELL32.dll!_SHCoCreateInstance+0x127
SHELL32.dll!SHCoCreateInstance+0x40
SHELL32.dll!DCA_CreateInstance+0x2c
SHELL32.dll!CFSIconOverlayManager::_LoadIconOverlayIdentifiers+0xd7
SHELL32.dll!CFSIconOverlayManager::_InitializeHdsaIconOverlays+0x33
SHELL32.dll!CFSIconOverlayManager::CreateInstance+0x3f
SHELL32.dll!CCF_CreateInstance+0x2b
SHELL32.dll!_CreateFromDllGetClassObject+0x2d
SHELL32.dll!_CreateFromShell+0x1b
SHELL32.dll!_SHCoCreateInstance+0x4e
SHELL32.dll!SHCoCreateInstance+0x40
SHELL32.dll!IconOverlayManagerInit+0x26
SHELL32.dll!GetIconOverlayManager+0x10
SHELL32.dll!_ShellImageListInit+0x29b
SHELL32.dll!FileIconInit+0x19b
SHELL32.dll!Shell_GetImageLists+0x14
COMDLG32.dll!OpenDlgProc+0x3f9
USER32.dll!InternalCallWinProc+0x28
USER32.dll!UserCallDlgProcCheckWow+0x146
USER32.dll!DefDlgProcWorker+0xa8
USER32.dll!DefDlgProcW+0x22
USER32.dll!InternalCallWinProc+0x28
USER32.dll!UserCallWinProcCheckWow+0xea
USER32.dll!SendMessageWorker+0x4a5
USER32.dll!SendMessageW+0x7f
COMCTL32.dll!ComboBox_CalcControlRects+0xbd
COMCTL32.dll!ComboBox_CreateHandler+0x102
COMCTL32.dll!ComboBox_WndProc+0x22d
USER32.dll!InternalCallWinProc+0x28
USER32.dll!UserCallWinProcCheckWow+0xea
USER32.dll!DispatchClientMessage+0xa3
USER32.dll!__fnINLPCREATESTRUCT+0x8b
ntdll.dll!KiUserCallbackDispatcher+0x13
USER32.dll!NtUserCreateWindowEx+0xc
USER32.dll!InternalCreateDialog+0x929
USER32.dll!InternalDialogBox+0xa9
USER32.dll!DialogBoxIndirectParamAorW+0x37
USER32.dll!DialogBoxIndirectParamW+0x1b
COMDLG32.dll!NewGetFileName+0x240
COMDLG32.dll!NewGetOpenFileName+0xf
COMDLG32.dll!GetFileName+0x35d
COMDLG32.dll!GetOpenFileNameW+0x62
xul.dll!gfxTextRun::AccumulatePartialLigatureMetrics+0x98d7
GDI32.dll!IcmDeleteLocalDC+0x21
nss3.dll!CERT_CheckNameSpace+0x280
ntkrnlpa.exe!NtInitialUserProcessBuffer+0x16
ntkrnlpa.exe!RtlUpcaseUnicodeString+0xa2
ntdll.dll!KiFastSystemCallRet
ntdll.dll!NtRemoveIoCompletion+0xc
kernel32.dll!GetQueuedCompletionStatus+0x29
xul.dll!gfxTextRunCache::MakeTextRun+0x3b9e
xul.dll!gfxTextRunCache::MakeTextRun+0x3b47
xul.dll!gfxPlatform::GetCMSsRGBProfile+0x8af
xul.dll!gfxWindowsPlatform::GetFontFamilyList+0x99c
xul.dll!gfxWindowsPlatform::GetFontFamilyList+0x9ae
xul.dll!NS_LogInit_P+0xb99
xul.dll!NS_LogInit_P+0xb35
xul.dll!NS_LogTerm_P+0x1e6
Toutes les réponses (2)
If this is the same as what has been seen in Thunderbird, then it's resolved by an MS-windows update according to http://getsatisfaction.com/mozilla_messaging/topics/crash_when_opening_message_containing_attachment ... but I don't know which MS update.
killing 'xul.dll!NS_LogTerm_P+0x...' via the MS Process Explorer reenables the file save/open dialog as well as the application menu in the extras/preferences dialog.
Problem is effective and reproducable since v3.1.4.
os: XPproSP3 x32
Modifié le