Closed Bug 1423554 Opened 7 years ago Closed 7 years ago

Error: We have already registered a distinct blocker with the same name: ReleasingTimerHolder in browser console when opening tabs

Categories

(Core :: DOM: File, defect)

Product:
Core
Component:
DOM: File
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1423485
Tracking Flags:
Tracking Status
firefox59 --- affected

People

(Reporter: Gijs, Unassigned)

References

Details

Looks like this may be related to bug 1420594. I don't have exact STR right now, trying to figure that out, but the error message seems pretty bad.
I can reliably repro like this:

1. start nightly on a clean profile
2. open browser console
3. open a new tab, load google.co.uk
4. open another new tab, load mozilla.org

(on macOS 10.13 if that makes a difference)
Marking this as blocking both of the bugs that show up in blame for me, not sure which one caused it off-hand. But naively, knowing nothing about the implementation here, the fact that we add these blockers in Create() suggests that in this sequence:

1. create one blob
2. create other blob
3. destroy first blob early
4. shutdown

we won't be destroying blob #2 because its shutdown blocker never got added.
Blocks: 1422314, 1420594
Flags: needinfo?(bkelly)
Flags: needinfo?(amarchesini)
Status: NEW → RESOLVED
Closed: 7 years ago
Flags: needinfo?(amarchesini)
Resolution: --- → DUPLICATE
Flags: needinfo?(bkelly)
You need to log in before you can comment on or make changes to this bug.