Closed
Bug 287158
Opened 20 years ago
Closed 20 years ago
use requests in xpinstall so that defining JS_PARANOID_REQUEST does not result in CHECK_REQUEST killing the app because of xpinstall tasks
Categories
(Core Graveyard :: Installer: XPInstall Engine, enhancement)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: timeless, Assigned: timeless)
Details
Attachments
(1 file)
|
9.44 KB,
patch
|
dveditz
:
review+
|
Details | Diff | Splinter Review |
summary statement: xpinstall (which is runs on background threads) violates the
js request api
the best links about this that i could find were:
http://www.mozilla.org/js/spidermonkey/apidoc/gen/api-JS_BeginRequest.html
http://archive.gingerall.cz/archives/public/sablot2004/msg00117.html
i can't really find much else about it (i have spoken with brendan and shaver
about it, although not in a long time)
fwiw, my process is not the cleanest, basically i built and ran w/ paranoid
request and patched until mozilla stopped being killed by spidermonkey.
js_paranoid_request is enforced by check_request
so any call to any jsapi.c function that does check_request needs to be in a request
[with a special gecko expcetion made for the main thread for performance reasons]
this is bug #1 of probably 5 or 6.
Attachment #178199 -
Flags: review?(dveditz)
Comment 2•20 years ago
|
||
Comment on attachment 178199 [details] [diff] [review]
wrap xpinstall jsapi calls in begin/end-request
r=dveditz
Attachment #178199 -
Flags: review?(dveditz) → review+
Comment on attachment 178199 [details] [diff] [review]
wrap xpinstall jsapi calls in begin/end-request
mozilla/xpinstall/src/nsJSInstall.cpp 1.115
mozilla/xpinstall/src/nsSoftwareUpdateRun.cpp 1.95
mozilla/xpinstall/src/nsXPITriggerInfo.cpp 1.28
Updated•20 years ago
|
Flags: blocking1.7.7?
Flags: blocking-aviary1.1+
Flags: blocking-aviary1.0.3?
Updated•20 years ago
|
Flags: blocking1.7.7?
Flags: blocking-aviary1.0.3?
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•