Summary: | REGRESSION: Using setTimeout.call or setTimeout.apply only works the first time is used | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Raul Hudea <rhudea> | ||||
Component: | JavaScriptCore | Assignee: | Nobody <webkit-unassigned> | ||||
Status: | RESOLVED FIXED | ||||||
Severity: | Normal | CC: | ap, mrowe, oliver, steve, zwarich | ||||
Priority: | P1 | Keywords: | HasReduction, InRadar, Regression | ||||
Version: | 528+ (Nightly build) | ||||||
Hardware: | All | ||||||
OS: | All | ||||||
Attachments: |
|
Description
Raul Hudea
2009-05-21 02:12:30 PDT
Created attachment 30533 [details]
Simple test case
Seems like one of Oliver's recent optimisations may have introduced this. *** Bug 23670 has been marked as a duplicate of this bug. *** This occurs in the 4.0 beta, so it's not Oliver's recent changes. It also impacts the interpreter -- i think it may be a bug in op_resolve_global, but that doesn't explain why it only seems to effect .call and .apply op_resolve_global is apparently broked. Got it, we're caching a property on the global objects prototype chain as if it were directly on the global object Committing to http://svn.webkit.org/repository/webkit/trunk ... M JavaScriptCore/ChangeLog M JavaScriptCore/interpreter/Interpreter.cpp M JavaScriptCore/jit/JITStubs.cpp M LayoutTests/ChangeLog A LayoutTests/fast/js/global-function-resolve-expected.txt A LayoutTests/fast/js/global-function-resolve.html A LayoutTests/fast/js/resources/global-function-resolve.js Committed r44016 |