Closed Bug 588808 Opened 15 years ago Closed 15 years ago

TabChildGlobal objects shouldn't be kept alive too long

Categories

(Core :: IPC, defect)

x86
All
defect
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: smaug, Assigned: smaug)

Details

Attachments

(1 file, 1 obsolete file)

Attached patch patch (obsolete) — Splinter Review
This applies both to e10s and non-e10s objects. We seem to keep them alive too long. Note, I really want to keep those DEBUG_smaug parts, at least for some time. And that is why I added mID. After this, E10s has still some problem with the first or last TabChildGlobal. It should be deleted earlier. But that is a different bug.
Attachment #467442 - Flags: review?
Attachment #467442 - Flags: review? → review?(azakai)
blocking2.0: --- → ?
Comment on attachment 467442 [details] [diff] [review] patch r+ without mID, printfs. that is what patch queues are for.
Attachment #467442 - Flags: review?(azakai)
Attachment #467442 - Flags: review+
Attachment #467442 - Flags: approval2.0?
Attached patch patchSplinter Review
Without my debug things
Attachment #467442 - Attachment is obsolete: true
Attachment #467481 - Flags: approval2.0?
Attachment #467442 - Flags: approval2.0?
Attachment #467481 - Flags: approval2.0? → approval2.0+
blocking2.0: ? → ---
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: