Closed Bug 973912 Opened 10 years ago Closed 10 years ago

crash in nsSocketInputStream::OnSocketReady(tag_nsresult)

Categories

(Core :: Networking, defect)

Product:
Core
Component:
Networking
Version:
30 Branch
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

()

Status:
VERIFIED DUPLICATE of bug 973207
Tracking Flags:
Tracking Status
firefox30 - affected

People

(Reporter: tracy, Unassigned)

References

Details

(Keywords: crash, topcrash)

Crash Data

This bug was filed from the Socorro interface and is 
report bp-9604e9ff-e608-466c-8e23-2d69b2140217.
=============================================================

more reports: https://crash-stats.mozilla.com/report/list?product=Firefox&signature=nsSocketInputStream%3A%3AOnSocketReady%28tag_nsresult%29#tab-reports

crash stats shows this regressed between Nightly builds 20140214 and 20140215: http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=d275eebfae04&tochange=b80f7eece913

Currently #13 on Nightly topcrash list, but with several high volume crashes above it already fixed, preemptively marking this topcrash. Seeing reports on all platforms
I don't see anything with a build id after 2/17 so I suspect this is a dup of 973207. let me know if the data contradicts.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
(In reply to Patrick McManus [:mcmanus] from comment #1)
> I don't see anything with a build id after 2/17 so I suspect this is a dup
> of 973207. let me know if the data contradicts.
> 
> *** This bug has been marked as a duplicate of bug 973207 ***

crash stats data confirms no reports with this signature on builds after 20140217
Status: RESOLVED → VERIFIED
Crash Signature: [@ nsSocketInputStream::OnSocketReady(tag_nsresult)] → [@ nsSocketInputStream::OnSocketReady(tag_nsresult)] [@ nsRefPtr<nsIRunnable>::~nsRefPtr<nsIRunnable>() | nsSocketInputStream::OnSocketReady(tag_nsresult) ]
Will not be tracking this since its a duplicate. Please nominate bug 973207 if you feel this needs attention from Relman.
You need to log in before you can comment on or make changes to this bug.