Closed Bug 588210 Opened 15 years ago Closed 9 years ago

Firefox 4.0b3 Crash [@ SockHandleAsyncIndication ]

Categories

(Core :: Networking, defect)

x86
Windows XP
defect
Not set
critical

Tracking

()

RESOLVED INCOMPLETE
Tracking Status
blocking2.0 --- -

People

(Reporter: cbook, Unassigned)

References

()

Details

(Keywords: crash, regression, Whiteboard: [crashkill]LSP)

Crash Data

new topcrash and new crash in Firefox 4 beta 3 @ Firefox 4.0b3 Crash Report [@ SockHandleAsyncIndication ] see http://crash-stats.mozilla.com/report/list?signature=SockHandleAsyncIndication so far windows only and looks like a startup crash
blocking2.0: --- → ?
Signature SockHandleAsyncIndication UUID eb7f12fd-ab2b-4664-8428-fd27b2100816 Time 2010-08-16 07:21:05.361704 Uptime 1 Last Crash 1 seconds before submission Install Age 193413 seconds (2.2 days) since version was first installed. Product Firefox Version 4.0b3 Build ID 20100805192522 Branch 2.0 OS Windows NT OS Version 5.1.2600 Service Pack 2 CPU x86 CPU Info GenuineIntel family 6 model 15 stepping 2 Crash Reason EXCEPTION_ACCESS_VIOLATION Crash Address 0x719d57f9 User Comments Processor Notes WARNING: Json file missing Add-ons EMCheckCompatibility False Related Bugs Crashing Thread Frame Module Signature [Expand] Source 0 @0x719d57f9 1 mswsock.dll SockHandleAsyncIndication 2 mswsock.dll SockAsyncThread 3 kernel32.dll BaseThreadStart This is probably an LSP. We have work to stop LSPs, unfortunately it isn't here yet. A quick look suggests to me this is only one user. Can you find an email address or evidence of multiple distinct cpus (model/stepping)?
maybe test case for lsp blocking that is coming in b4.
Whiteboard: [crashkill] → [crashkill]LSP
blocking2.0: ? → -
Crash Signature: [@ SockHandleAsyncIndication ]
One of these on 7.0.1 in the past 4 weeks.
only one crash in one month bp-57fe3ccd-fae1-4da6-862f-2d8e32160105 not much of a stack 0 mswsock.dll SockHandleAsyncIndication not sure this is worth keeping open
Component: General → Networking
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.