Thread mismatch assertion when hitting minimize memory

RESOLVED DUPLICATE of bug 1239794

Status

()

Toolkit
Storage
RESOLVED DUPLICATE of bug 1239794
8 months ago
8 months ago

People

(Reporter: mccr8, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(2 attachments)

(Reporter)

Description

8 months ago
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

8 months ago
Group: dom-core-security → toolkit-core-security
Component: XPCOM → Storage
Product: Core → Toolkit
(Reporter)

Comment 1

8 months ago
Created attachment 8859355 [details]
assertion stack
(Reporter)

Comment 2

8 months ago
Created attachment 8859356 [details]
Other storage stack

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.
It looks like the same as bug 1239794
(Reporter)

Updated

8 months ago
Group: toolkit-core-security
Status: NEW → RESOLVED
Last Resolved: 8 months ago
Resolution: --- → DUPLICATE
Duplicate of bug: 1239794
You need to log in before you can comment on or make changes to this bug.