Closed
Bug 971893
Opened 10 years ago
Closed 10 years ago
crash in mozilla::net::nsHttpConnectionMgr::OnMsgCancelTransaction(int, void*)
Categories
(Core :: Networking: HTTP, defect)
Core
Networking: HTTP
Tracking
()
VERIFIED
FIXED
mozilla30
Tracking | Status | |
---|---|---|
firefox27 | --- | unaffected |
firefox28 | --- | unaffected |
firefox29 | --- | unaffected |
firefox30 | + | verified |
People
(Reporter: bzumwalt, Assigned: mcmanus)
References
Details
(Keywords: crash, regression, topcrash-win, Whiteboard: [b2g-crash])
Crash Data
Attachments
(1 file)
1.68 KB,
patch
|
u408661
:
review+
|
Details | Diff | Splinter Review |
This bug was filed from the Socorro interface and is report bp-83eaeb34-2a72-45b8-8974-aae962140212. ============================================================= crash in mozilla::net::nsHttpConnectionMgr::OnMsgCancelTransaction(int, void*) Description: Issue occurred while closing tab in browser app while receiving very large bluetooth file transfer (15+ minute .3gp file). Will investigate further, no solid STR at this time. Environmental Variables: Device: Buri v1.4 Master Mozilla RIL BuildID: 20140212040203 Gaia: 4c6b5142d3b716f1c4ea502eeb92d3119f2b01c6 Gecko: 802d87c77e76 Version: 30.0a1 Firmware Version: V1.2-device.cfg
Updated•10 years ago
|
Component: General → Networking
Product: Firefox OS → Core
Whiteboard: [b2g-crash]
Version: unspecified → Trunk
Comment 1•10 years ago
|
||
Leaving needinfo on you to see if you can get consistent STR
Flags: needinfo?(bzumwalt)
Reporter | ||
Comment 2•10 years ago
|
||
Could not replicate to get good STR. Attempted following scenarios: - Exact same state with closing crashed tab in browser w/o bluetooth transfer in background - Same bluetooth transfer (.3gp, 15+ minute rt, 25+ MB size) w/o browser open - Exact same state for browser described in bullet 1 while running bluetooth transfer described above in background Monitoring logcat output during tests revealed multiple out of PMEM messages during all scenarios involving browser, but no crash was produced.
Flags: needinfo?(bzumwalt)
Doesn't seem specific to B2G, as there are ~200 desktop reports as well.
OS: Gonk (Firefox OS) → All
Hardware: ARM → All
Comment 4•10 years ago
|
||
Yes, this is the top crash on Firefox Nightly in the last day.
tracking-firefox30:
--- → ?
Keywords: topcrash-win
Assignee | ||
Comment 5•10 years ago
|
||
thanks for the bug report.. regression from 970279.. ent needs to be checked for null
Depends on: 970279
Assignee | ||
Updated•10 years ago
|
Component: Networking → Networking: HTTP
Assignee | ||
Comment 6•10 years ago
|
||
Attachment #8375547 -
Flags: review?(hurley)
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → mcmanus
Status: NEW → ASSIGNED
Assignee | ||
Comment 7•10 years ago
|
||
Comment on attachment 8375547 [details] [diff] [review] crash in onMsgCancelTransaction Review of attachment 8375547 [details] [diff] [review]: ----------------------------------------------------------------- I'm not sure why bzexport assigns reviews to hurley@mozilla.com when I do -r :hurley
Attachment #8375547 -
Flags: review?(hurley) → review?(hurley)
Attachment #8375547 -
Flags: review?(hurley) → review+
Assignee | ||
Comment 8•10 years ago
|
||
https://bugzilla.mozilla.org/show_bug.cgi?id=917893
Assignee | ||
Comment 9•10 years ago
|
||
(In reply to Patrick McManus [:mcmanus] from comment #8) > https://bugzilla.mozilla.org/show_bug.cgi?id=917893 that was a brilliant comment :) remote: https://hg.mozilla.org/integration/mozilla-inbound/rev/5dd0f145d79d
Comment 10•10 years ago
|
||
bp-a510b6ca-5e88-4e0d-b779-232242140213 I could not reproduce
https://hg.mozilla.org/mozilla-central/rev/5dd0f145d79d
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla30
Updated•10 years ago
|
Comment 12•10 years ago
|
||
We are going to track this in case it comes up again
Assignee | ||
Updated•10 years ago
|
status-firefox27:
--- → unaffected
status-firefox28:
--- → unaffected
status-firefox29:
--- → unaffected
status-firefox30:
--- → fixed
Comment 14•10 years ago
|
||
There are but 2 crashes on Nightly desktop with builds after the fix here was checked in on 20140213. And one of those crashed has the poisoned memory location.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•