[e10s] consider wiping static mem after a tab crash, or look at auditing code for such bugs

NEW
Unassigned

Status

()

Firefox
General
P3
normal
3 years ago
2 years ago

People

(Reporter: jib, Unassigned)

Tracking

40 Branch
Points:
---

Firefox Tracking Flags

(e10s+)

Details

Sample Bug 1205339.

12:43:37 -  jib:	 so there's no plan to wipe the static space then
12:43:44 -  mconley|livehacking:	 jib: likely there are statics where it makes sense to flush them, and others where it does not
12:43:50 -  mconley|livehacking:	 jib: might be worth auditing at some point
12:44:09 -  mconley|livehacking:	 couldn't hurt to file a bug on it just so we don't lose track
12:44:10 -  jimm: jib: haven't seen a bug on that, you could file and drop it into e10s triage. the team can discuss.
12:44:12 -  mconley|livehacking:	 because it's a good idea
tracking-e10s: ? → +

Comment 1

2 years ago
Hi Jan-Ivar Bruaroey,
We are cleaning up untriaged items. Please assist us by selecting an appropriate component. Thanks
Flags: needinfo?(jib)
Hi Abe, I have no idea which component this would be.
Flags: needinfo?(jib)

Updated

2 years ago
Component: Untriaged → General

Updated

2 years ago
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.