Closed Bug 746548 Opened 12 years ago Closed 12 years ago

crash in nsCacheService::Lock

Categories

(Core :: Networking: Cache, defect)

Product:
Core
Component:
Networking: Cache
Version:
14 Branch
Platform:
ARM
Android
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

()

Status:
RESOLVED FIXED
Milestone:
mozilla14
Tracking Flags:
Tracking Status
blocking-fennec1.0 --- beta+

People

(Reporter: csuciu, Assigned: bnicholson)

References

Details

(Keywords: crash, regression, topcrash, Whiteboard: [native-crash][mobile-crash])

Crash Data

Attachments

(1 file)

patch
2.12 KB, patch
mfinkle
: review+
Details | Diff | Splinter Review 
This bug was filed from the Socorro interface and is 
report bp-b43ea2d1-2179-42b5-bd4e-bf9742120418 .
=============================================================
Component: General → Networking: Cache
Product: Fennec Native → Core
QA Contact: general → networking.cache
Version: Firefox 14 → Trunk
Did bug 745075 land in m-c in time to potential be related to this?
It first appeared in 14.0a1/20120418030652. The regression range is:
http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=c61e7c3a232a&tochange=0c7e2911be75
bug 745075 is in the regression range.
Blocks: 745075
Keywords: regression, topcrash
Whiteboard: [native-crash][mobile-crash]
Version: Trunk → 14 Branch
blocking-fennec1.0: --- → ?
Bug 746697 related?
(In reply to Martijn Wargers [:mw22] (QA - IRC nick: mw22) from comment #3)
> Bug 746697 related?
I don't think so because bug 746697 happens also in 11.0 on Mac OS X.
Attached patch patch — — Splinter Review 
It looks like the cache service is lazily loaded, so gService (the global cache instance) isn't set until a page is loaded.

STR in Nightly:
1) Open Fennec, stay at about:home
2) Push home
Assignee: nobody → bnicholson
Status: NEW → ASSIGNED
Attachment #616253 - Flags: review?(gbrown)
Attachment #616253 - Flags: review?(gbrown) → review+
marking beta+ to fix the crash. low risk fix.
blocking-fennec1.0: ? → beta+
blocking-fennec1.0: ? → beta+
Just asking, because I see this same issue in Android XUL builds.  Would this issue effect both and will this fix it for both?
https://hg.mozilla.org/mozilla-central/rev/f6edc3d72a22
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla14
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: