Closed
Bug 627306
Opened 13 years ago
Closed 13 years ago
UMR with dispatchEvent
Categories
(Core :: DOM: Events, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: jruderman, Assigned: jruderman)
Details
(Keywords: testcase, valgrind, Whiteboard: [sg:low?])
Attachments
(4 files)
310 bytes,
text/html
|
Details | |
973 bytes,
text/plain
|
Details | |
40.13 KB,
text/plain
|
Details | |
799 bytes,
patch
|
smaug
:
review+
sdwilsh
:
approval2.0+
|
Details | Diff | Splinter Review |
With this testcase, Valgrind complains of uninitialized memory from nsIDOMEventTarget_DispatchEvent making its way into js::Interpret. And lo, if I print the return value from dispatchEvent, sometimes I get true and sometimes I get false, seemingly at random. http://hg.mozilla.org/mozilla-central/annotate/80c4d7317c29/content/events/src/nsEventListenerManager.cpp#l1316 returns NS_OK without setting _retval, so it's suspicious.
Assignee | ||
Comment 1•13 years ago
|
||
Assignee | ||
Comment 2•13 years ago
|
||
Comment 3•13 years ago
|
||
Looks like a regression from quickstubs...
Comment 4•13 years ago
|
||
Er, no, this is ancient.
Assignee | ||
Comment 5•13 years ago
|
||
What's the correct behavior? Set the retval to true, I guess? http://www.w3.org/TR/DOM-Level-2-Events/events.html#Events-EventTarget-dispatchEvent
Comment 6•13 years ago
|
||
Yeah
Assignee | ||
Updated•13 years ago
|
Whiteboard: [sg:low?]
Assignee | ||
Comment 7•13 years ago
|
||
Assignee | ||
Comment 8•13 years ago
|
||
This patch makes the Valgrind complaint go away for me.
Updated•13 years ago
|
Attachment #505690 -
Flags: review?(Olli.Pettay) → review+
Assignee | ||
Updated•13 years ago
|
Attachment #505690 -
Flags: approval2.0?
Updated•13 years ago
|
Attachment #505690 -
Flags: approval2.0? → approval2.0+
Assignee | ||
Comment 9•13 years ago
|
||
http://hg.mozilla.org/mozilla-central/rev/e3b9490af708
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Updated•9 years ago
|
Group: core-security → core-security-release
Updated•9 years ago
|
Group: core-security-release
You need to log in
before you can comment on or make changes to this bug.
Description
•