Modify JS engine so that XPConnect can directly monitor object creation and deletion, helps with double free problems, perf etc.? We should make it impossible to run code in safe context Is it possible we might elevate privileges during GC? SOAP generates stuff dynamically, some names can be easily guessed Is it possible to generate JS exceptions that cross the chrome boundary and end up being run with chrome privileges?
I'm going to start creating bugs off this as I find them.
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla1.4beta
16 years ago
Just a note, bug 202889 deals with issue one. I believe issue one incorrectly states object, it should talk about JSContexts. We already know when JS objects are finalized and we don't really need to know when they are created.
Target Milestone: mozilla1.4beta → mozilla1.5alpha
Moving out, speak up if you believe this needs to be considered for 1.5b
Target Milestone: mozilla1.5beta → mozilla1.6alpha
Target Milestone: mozilla1.6alpha → mozilla1.7alpha
Status: ASSIGNED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.