Closed
Bug 1357554
Opened 7 years ago
Closed 7 years ago
Thread mismatch assertion when hitting minimize memory
Categories
(Toolkit :: Storage, defect)
Toolkit
Storage
Tracking
()
RESOLVED
DUPLICATE
of bug 1239794
People
(Reporter: mccr8, Unassigned)
Details
Attachments
(2 files)
I've gotten this a few times today, in an m-c from yesterday. STR: start the browser, open a page, open about:memory, hit minimize memory usage. I'll attach the stack, but it looks like on the main thread we're dispatching the memory pressure thing from the observer service, which ends up in mozilla::storage::Service::minimizeMemory(), which then does a dispatch, which ends up in mozilla::LazyIdleThread::OnDispatchedEvent, and then we hit this assert.
Reporter | ||
Updated•7 years ago
|
Group: dom-core-security → toolkit-core-security
Component: XPCOM → Storage
Product: Core → Toolkit
Reporter | ||
Comment 1•7 years ago
|
||
Reporter | ||
Comment 2•7 years ago
|
||
I also see this stack at startup sometimes, in this profile, so maybe the profile is just messed up? This is a default profile generated by mach run.
Comment 3•7 years ago
|
||
It looks like the same as bug 1239794
Reporter | ||
Updated•7 years ago
|
Group: toolkit-core-security
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•