Closed
Bug 392895
Opened 17 years ago
Closed 13 years ago
Confusing "access violation writing location", when exiting JAWS with Firefox running
Categories
(Core :: Disability Access APIs, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: aaronlev, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: access, regression)
1) Launch the JAWS screen reader
2) Run Firefox in Visual Studio
3) Try to exit Firefox
You will get this crash:
First-chance exception at 0x03a24bfa in firefox.exe: 0xC0000005: Access violation writing location 0x8007ef50.
At this stack:
> kernel32.dll!_RaiseException@16() + 0x53 bytes
rpcrt4.dll!_RpcpRaiseException@4() + 0x21 bytes
rpcrt4.dll!_NdrProxySendReceive@8() + 0x112c bytes
rpcrt4.dll!_NdrClientCall2() + 0x9dc bytes
rpcrt4.dll!_ObjectStublessClient@8() + 0x5d bytes
rpcrt4.dll!_ObjectStubless@0() + 0xf bytes
FsDomSrv.dll!058d95b7()
[Frames below may be incorrect and/or missing, no symbols loaded for FsDomSrv.dll]
FsDomSrv.dll!058c2933()
FsDomSrv.dll!058dcb07()
FsDomSrv.dll!058dcb4d()
FsDomSrv.dll!058dcb3f()
ole32.dll!CStdIdentity::ReleaseCtrlUnk() + 0x46 bytes
ole32.dll!CStdMarshal::Disconnect() + 0x1d6 bytes
ole32.dll!CStdMarshal::HandlePendingDisconnect() + 0x461c bytes
ole32.dll!CRemoteUnknown::RemReleaseWorker() + 0x155 bytes
ole32.dll!CRemoteUnknown::RemRelease() + 0x15 bytes
rpcrt4.dll!_Invoke@12() + 0x30 bytes
rpcrt4.dll!_NdrStubCall2@16() + 0x215 bytes
rpcrt4.dll!_CStdStubBuffer_Invoke@12() + 0x82 bytes
ole32.dll!SyncStubInvoke() + 0x33 bytes
ole32.dll!StubInvoke() + 0x73 bytes
ole32.dll!CCtxComChnl::ContextInvoke() + 0xd2 bytes
ole32.dll!MTAInvoke() + 0x1a bytes
ole32.dll!STAInvoke() + 0x4e bytes
ole32.dll!AppInvoke() + 0x3a0 bytes
ole32.dll!ComInvokeWithLockAndIPID() + 0x23d bytes
ole32.dll!ComInvoke() + 0x5a bytes
ole32.dll!ThreadDispatch() + 0x1a bytes
ole32.dll!ThreadWndProc() + 0x93 bytes
user32.dll!_InternalCallWinProc@20() + 0x28 bytes
user32.dll!_UserCallWinProcCheckWow@32() + 0xb7 bytes
user32.dll!_DispatchMessageWorker@8() + 0xdc bytes
user32.dll!_DispatchMessageW@4() + 0xf bytes
gkwidget.dll!nsAppShell::ProcessNextNativeEvent(int mayWait=0x00000001) Line 149 C++
gkwidget.dll!nsBaseAppShell::DoProcessNextNativeEvent(int mayWait=0x00000001) Line 137 + 0x11 bytes C++
gkwidget.dll!nsBaseAppShell::OnProcessNextEvent(nsIThreadInternal * thr=0x00d8ff70, int mayWait=0x00000001, unsigned int recursionDepth=0x00000000) Line 247 + 0xf bytes C++
xpcom_core.dll!nsThread::ProcessNextEvent(int mayWait=0x00000001, int * result=0x0012fa00) Line 480 C++
xpcom_core.dll!NS_ProcessNextEvent_P(nsIThread * thread=0x00d8ff70, int mayWait=0x00000001) Line 227 + 0x16 bytes C++
gkwidget.dll!nsBaseAppShell::Run() Line 154 + 0xc bytes C++
tkitcmps.dll!nsAppStartup::Run() Line 170 + 0x1c bytes C++
xul.dll!XRE_main(int argc=0x00000004, char * * argv=0x00d8af30, const nsXREAppData * aAppData=0x00d8b398) Line 3060 + 0x25 bytes C++
firefox.exe!main(int argc=0x00000004, char * * argv=0x00d8af30) Line 153 + 0x12 bytes C++
firefox.exe!__tmainCRTStartup() Line 586 + 0x19 bytes C
firefox.exe!mainCRTStartup() Line 403 C
kernel32.dll!_BaseProcessStart@4() + 0x23 bytes
Flags: blocking1.9?
Reporter | ||
Comment 1•17 years ago
|
||
Step 3 was wrong, it should say:
3. Exit JAWS (Insert+F4)
Summary: Confusing "access violation writing location", when exiting Firefox with JAWS running → Confusing "access violation writing location", when exiting JAWS with Firefox running
Reporter | ||
Updated•17 years ago
|
Severity: normal → critical
Reporter | ||
Updated•17 years ago
|
Blocks: fox3access
Reporter | ||
Comment 2•17 years ago
|
||
Before the access violation I get:
"First-chance exception at 0x7c812a5b (kernel32.dll) in firefox.exe: 0x80010108: The object invoked has disconnected from its clients."
The exception's code matches RPC_E_DISCONNECTED. I haven't found anything useful about it by searching the net.
This only happens when you run in the debugger. Therefore, not a blocker.
No longer blocks: fox3access
Comment 5•13 years ago
|
||
Is thisstill a problem?
Comment 6•13 years ago
|
||
I've never seen a problem and can't see it on trunk.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•