Closed Bug 868619 Opened 11 years ago Closed 11 years ago

Should we backout poisoning nsView from all branches?

Categories

(Core :: Web Painting, enhancement)

Product:
Core
Component:
Web Painting
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED INVALID
Tracking Flags:
Tracking Status
firefox22 - ---
firefox23 - ---

People

(Reporter: akeybl, Assigned: MatsPalmgren_bugz)

References

Details

Probably will make FF22 less stable than it needs to be - let's back it out from all branches asap once we have more data.

+++ This bug was initially created as a clone of Bug #865569 +++

This is to mitigate crashes like bug 850571 to some degree,
and to make the crash more likely to occur so we can get STR.
Any instability because of this is a potential sg:crit. I cannot think of any reason we would disable this poisoning unless 1) it exposes a very high topcrash 2) which we cannot fix this cycle.

I strongly oppose this (note bug 860254 where we are hoping to poison all small-memory frees).
Keywords: sec-want
Thanks Benjamin.
Status: NEW → RESOLVED
Closed: 11 years ago
tracking-firefox22: ? → -
tracking-firefox23: ? → -
Resolution: --- → INVALID
Group: core-security
Component: Layout: View Rendering → Layout: Web Painting
You need to log in before you can comment on or make changes to this bug.