Closed
Bug 113949
Opened 23 years ago
Closed 23 years ago
Trunk M096 crash [@ nsFileTransport::Process] [@ nsProxyObject::Post]
Categories
(Core :: Networking, defect, P1)
Tracking
()
RESOLVED
FIXED
mozilla0.9.7
People
(Reporter: jay, Assigned: darin.moz)
References
Details
(Keywords: crash, topcrash, Whiteboard: [patch needs sr=])
Crash Data
Attachments
(1 file)
4.26 KB,
patch
|
dougt
:
review+
mscott
:
superreview+
|
Details | Diff | Splinter Review |
There are a few of these crashes in recent MozillaTrunk builds. The stack trace is only one line, so I don't know how helpful it will be in debugging...but here's the latest from Talkback: [ 8 nsFileTransport::Process 5b97409e - nsFileTransport::Process ] Crash date range: 2001-12-03 to 2001-12-05 Min/Max Seconds since last crash: 539 - 337595 Min/Max Runtime: 4435 - 337595 Keyword List : Count Platform List 6 Windows NT 5.0 build 2195 2 Windows 98 4.90 build 73010104 Count Build Id List 2 2001120309 1 2001120506 1 2001120306 1 2001120211 1 2001113009 1 2001113006 1 2001112914 No of Unique Users 8 Stack trace(Frame) nsFileTransport::Process [d:\builds\seamonkey\mozilla\netwerk\base\src\nsFileTransport.cpp line 853] (66040) URL: back 2 google.com from www.aceweekly.com (66040) Comments: back from www.aceweekly.com to google..first crash in a long to tho!!! (27179) URL: www.amiga.org & www.x13design.com/bipolar/ (27179) Comments: www.x13design.com/bipolar/ had stalled during loading i attempted to open a new navigator window using the QuickLaunch menu (in the taskbar) and the browser crashed as www.amiga.org was trying to load. (9781) Comments: mapquest I'll update this with more info as I get it.
Reporter | ||
Updated•23 years ago
|
Doug, Darin, Should bbaetz be getting this bug? Who is looking at FileTransport stuff now? Neeti
Assignee | ||
Comment 2•23 years ago
|
||
-> me (i'll look into this... i recently made some changes that /might/ have resulted in this)
Assignee | ||
Comment 4•23 years ago
|
||
-> 0.9.7 (maybe)
Status: NEW → ASSIGNED
Priority: -- → P1
Target Milestone: --- → mozilla0.9.7
Assignee | ||
Comment 5•23 years ago
|
||
not much of a stack trace... if only there was a line number ;)
Assignee | ||
Comment 6•23 years ago
|
||
-> moz 1.0 (until we have more info)
Target Milestone: mozilla0.9.7 → mozilla1.0
Assignee | ||
Updated•23 years ago
|
Keywords: mozilla1.0
Assignee | ||
Comment 7•23 years ago
|
||
this talkback link http://climate/reports/SingleIncidentInfo.cfm?dynamicBBID=159724 gives this stack trace: nsFileTransport::Process [d:\builds\seamonkey\mozilla\netwerk\base\src\nsFileTransport.cpp, line 853] nsFileTransport::Run [d:\builds\seamonkey\mozilla\netwerk\base\src\nsFileTransport.cpp, line 637] nsThreadPoolRunnable::Run [d:\builds\seamonkey\mozilla\xpcom\threads\nsThread.cpp, line 908] nsThread::Main [d:\builds\seamonkey\mozilla\xpcom\threads\nsThread.cpp, line 136] _PR_NativeRunThread [../../../../../pr/src/threads/combined/pruthr.c, line 435] msvcrt.dll + 0x27fb8 (0x77c37fb8) kernel32.dll + 0x202ed (0x77e802ed)
Assignee | ||
Comment 8•23 years ago
|
||
i know exactly what the problem is... i fixed a similar bug in the socket transport. the problem is that the file transport's notification callbacks can be cleared from the UI thread while the file transport is using them on a file transport thread. we just need to protect nsFileTransport::mProgressSink with the file transport's lock. -> 0.9.7 (patch in hand)
Target Milestone: mozilla1.0 → mozilla0.9.7
Assignee | ||
Comment 9•23 years ago
|
||
this patch should fix this crash.
Assignee | ||
Comment 10•23 years ago
|
||
dougt: can you r= this patch? thx!
Comment 11•23 years ago
|
||
Comment on attachment 60859 [details] [diff] [review] v1.0 patch fine.
Attachment #60859 -
Flags: review+
Assignee | ||
Updated•23 years ago
|
Whiteboard: [patch needs sr=]
Assignee | ||
Comment 12•23 years ago
|
||
*** Bug 107843 has been marked as a duplicate of this bug. ***
Comment 13•23 years ago
|
||
Comment on attachment 60859 [details] [diff] [review] v1.0 patch sr=mscott pending the answer to my question. I couldn't quite tell from the context of the diff why we had to add a lock on mLock in SetNotificationsCallbacks in addtion to passing in the progress event sink each time into ::Process
Attachment #60859 -
Flags: superreview+
Assignee | ||
Comment 14•23 years ago
|
||
mscott: SetNotificationCallbacks can be called on the main thread, while Process is running, and assignment into a COMPtr is not atomic... there's the assignment of the pointer value (which is atomic) and then there's also the AddRef call. together these aren't atomic, so we need to protect all access to mProgressSink.
Assignee | ||
Comment 15•23 years ago
|
||
fixed-on-trunk
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 16•23 years ago
|
||
*** Bug 104761 has been marked as a duplicate of this bug. ***
Reporter | ||
Comment 17•23 years ago
|
||
Adding M096 and [@ nsProxyObject::Post] to summary for tracking, since bug 107843 was marked a dup.
Summary: Trunk crash [@ nsFileTransport::Process] → Trunk M096 crash [@ nsFileTransport::Process] [@ nsProxyObject::Post]
Comment 18•23 years ago
|
||
*** Bug 112729 has been marked as a duplicate of this bug. ***
Reporter | ||
Comment 19•23 years ago
|
||
*** Bug 112729 has been marked as a duplicate of this bug. ***
Comment 20•22 years ago
|
||
*** Bug 107214 has been marked as a duplicate of this bug. ***
Updated•13 years ago
|
Crash Signature: [@ nsFileTransport::Process]
[@ nsProxyObject::Post]
You need to log in
before you can comment on or make changes to this bug.
Description
•