Closed Bug 763392 Opened 12 years ago Closed 9 years ago

crash in nsHttpConnection::OnReadSegment @ nspr4 with Korean Input Method Editors

Categories

(Core :: Networking: HTTP, defect)

14 Branch
x86
Windows NT
defect
Not set
critical

Tracking

()

RESOLVED DUPLICATE of bug 671468

People

(Reporter: scoobidiver, Unassigned)

References

Details

(Keywords: crash)

Crash Data

It's #47 top browser crasher in 14.0b6. Here are correlations per module: SocketWrite | nspr4.dll@0x2a3f|EXCEPTION_ACCESS_VIOLATION_READ (157 crashes) 72% (113/157) vs. 1% (138/23847) IMKR12.IME 31% (49/157) vs. 0% (54/23847) 12.0.4518.0 5% (8/157) vs. 0% (9/23847) 12.0.6416.0 36% (56/157) vs. 0% (75/23847) 12.0.6600.0 24% (37/157) vs. 0% (53/23847) imekr61.ime 0% (0/157) vs. 0% (2/23847) 6.1.2600.2 24% (37/157) vs. 0% (51/23847) 6.1.2600.3 Signature nspr4.dll@0x2a3f More Reports Search UUID 5794a8dd-491c-469d-9d59-48ed02120611 Date Processed 2012-06-11 05:12:53 Uptime 184 Last Crash 3.1 minutes before submission Install Age 2.4 days since version was first installed. Install Time 2012-06-08 19:33:52 Product Firefox Version 14.0 Build ID 20120605113340 Release Channel beta OS Windows NT OS Version 5.1.2600 Service Pack 3 Build Architecture x86 Build Architecture Info GenuineIntel family 6 model 23 stepping 10 Crash Reason EXCEPTION_ACCESS_VIOLATION_READ Crash Address 0xc254000 App Notes AdapterVendorID: 0x1002, AdapterDeviceID: 0x68d9, AdapterSubsysID: 035c1043, AdapterDriverVersion: 8.690.0.0 D3D10 Layers? D3D10 Layers- D3D9 Layers? D3D9 Layers- EMCheckCompatibility True Total Virtual Memory 2147352576 Available Virtual Memory 1884491776 System Memory Use Percentage 31 Available Page File 3577798656 Available Physical Memory 1465888768 Frame Module Signature Source 0 @0x1751f2 1 @0x161b0e 2 nspr4.dll nspr4.dll@0x2a3f 3 xul.dll nsSocketOutputStream::Write netwerk/base/src/nsSocketTransport2.cpp:587 4 xul.dll nsHttpConnection::OnReadSegment netwerk/protocol/http/nsHttpConnection.cpp:1190 5 xul.dll nsHttpPipeline::ReadFromPipe netwerk/protocol/http/nsHttpPipeline.cpp:682 6 xul.dll nsPipeInputStream::ReadSegments xpcom/io/nsPipe3.cpp:799 7 xul.dll nsHttpPipeline::ReadSegments netwerk/protocol/http/nsHttpPipeline.cpp:726 8 xul.dll nsHttpConnection::OnSocketWritable netwerk/protocol/http/nsHttpConnection.cpp:1251 9 xul.dll nsHttpConnection::OnOutputStreamReady netwerk/protocol/http/nsHttpConnection.cpp:1530 10 xul.dll nsHttpConnection::Activate netwerk/protocol/http/nsHttpConnection.cpp:396 11 xul.dll nsHttpConnectionMgr::DispatchTransaction netwerk/protocol/http/nsHttpConnectionMgr.cpp:1512 12 xul.dll nsHttpConnectionMgr::TryDispatchTransaction netwerk/protocol/http/nsHttpConnectionMgr.cpp:1432 13 xul.dll nsHttpConnectionMgr::ProcessNewTransaction netwerk/protocol/http/nsHttpConnectionMgr.cpp:1617 14 xul.dll nsHttpConnectionMgr::OnMsgNewTransaction netwerk/protocol/http/nsHttpConnectionMgr.cpp:1781 15 xul.dll nsHttpConnectionMgr::nsConnEvent::Run netwerk/protocol/http/nsHttpConnectionMgr.h:522 16 xul.dll nsThread::ProcessNextEvent xpcom/threads/nsThread.cpp:656 17 xul.dll NS_ProcessNextEvent_P obj-firefox/xpcom/build/nsThreadUtils.cpp:245 18 xul.dll nsSocketTransportService::Run netwerk/base/src/nsSocketTransportService2.cpp:652 19 xul.dll nsThread::ProcessNextEvent xpcom/threads/nsThread.cpp:656 20 xul.dll nsThread::ThreadFunc xpcom/threads/nsThread.cpp:289 21 nspr4.dll _PR_NativeRunThread nsprpub/pr/src/threads/combined/pruthr.c:426 22 nspr4.dll pr_root nsprpub/pr/src/md/windows/w95thred.c:122 23 msvcr100.dll _callthreadstartex f:\dd\vctools\crt_bld\self_x86\crt\src\threadex.c:314 24 msvcr100.dll _threadstartex f:\dd\vctools\crt_bld\self_x86\crt\src\threadex.c:292 25 kernel32.dll BaseThreadStart More reports at: https://crash-stats.mozilla.com/report/list?signature=nspr4.dll%400x2a3f
Depends on: 671468
I think this is a dup of 671468.. The pipeline changes in FF14 have changed the stack a little bit, but the underlying pattern is still the same. not a new issue.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.