Open
Bug 1037245
Opened 12 years ago
Updated 1 year ago
Eval cache does not work unless the eval is wrapped in a function
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
NEW
People
(Reporter: gupta.rajagopal, Unassigned)
References
(Blocks 1 open bug)
Details
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Firefox/31.0 (Beta/Release)
Build ID: 20140623175014
Steps to reproduce:
In lldb, set a breakpoint at IsEvalCacheCandidate. Then, in the js shell:
var a = [];
for (var i = 0; i < 2; i++)
a[i] = eval("print('hello world')");
Actual results:
The breakpoint was never hit. In ~EvalScriptGuard, if (lookup_.str) failed, and IsEvalCacheCandidate was never called.
Expected results:
IsEvalCacheCandidate should be called, and the eval should be cached.
Updated•4 years ago
|
Severity: normal → S3
Updated•1 year ago
|
Blocks: sm-runtime
You need to log in
before you can comment on or make changes to this bug.
Description
•