Closed
Bug 625438
Opened 15 years ago
Closed 15 years ago
JM: watch handler is not always called
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
Tracking | Status | |
---|---|---|
blocking2.0 | --- | betaN+ |
People
(Reporter: jandem, Assigned: dvander)
References
Details
(Whiteboard: [hardblocker][fixed-in-tracemonkey])
Attachments
(1 file)
1.14 KB,
patch
|
jorendorff
:
review+
|
Details | Diff | Splinter Review |
Testcase:
--
var count = 0;
watch("x", function() {
count++;
});
for(var i=0; i<10; i++) {
x = 2;
}
print(count);
--
Output:
-m: 1
-j: 10
interp: 10
Reporter | ||
Comment 1•15 years ago
|
||
Btw adding a print('test'); statement inside the handler makes it print 2 instead of 1.
blocking2.0: --- → ?
![]() |
Assignee | |
Comment 2•15 years ago
|
||
Method JIT is testing getterness instead of setterness in SetGlobalName().
![]() |
||
Updated•15 years ago
|
Whiteboard: hardblocker
Updated•15 years ago
|
blocking2.0: ? → betaN+
Comment 3•15 years ago
|
||
Comment on attachment 503558 [details] [diff] [review]
fix
Yecch, that's a gross bug. Looks like exactly the right fix.
Attachment #503558 -
Flags: review?(jorendorff) → review+
![]() |
Assignee | |
Comment 4•15 years ago
|
||
Whiteboard: hardblocker → [hardblocker][fixed-in-tracemonkey]
Reporter | ||
Comment 5•15 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•