Closed Bug 1036692 Opened 11 years ago Closed 11 years ago

single-thread deadlock of CacheStorageService:mLock after hitting "Measure" in about:memory

Categories

(Core :: Networking: Cache, defect)

x86_64
Linux
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: dbaron, Assigned: mayhemer)

References

Details

(Keywords: hang)

Attachments

(2 files)

Attached file debugging
I was trying to debug why my session had gotten bogged down, and went to about:memory, and about:memory crashed because of what appears to be a single-thread deadlock in the cache, although gdb wasn't kind enough to give me the whole stack. I was running mozilla-central revision afa67a2f7905 plus my patch queue as of state https://hg.mozilla.org/users/dbaron_mozilla.com/patches/rev/74252f4f5cbc pushed up to the patch share-find-reference-frame. I'll attach what I got out of gdb.
Component: Networking: Cookies → Networking: Cache
Isn't think dup of bug 991669?
No it's not duplicate of that bug. The word CRASH confused me first.
Going to take a look. trace-malloc enabled build would give the whole stack in the deadlock detector warning. But would be super-slow...
Assignee: nobody → honzab.moz
Attached file debugging, again
I hit it a second time, again trying to open the slow script dialog during about:memory.
(I think I hit this much more reliably if I check the "Verbose" checkbox before hitting Measure.)
David, are you still able to reproduce this?
Flags: needinfo?(dbaron)
Closing for insufficient data.
Status: NEW → RESOLVED
Closed: 11 years ago
Flags: needinfo?(dbaron)
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: