Closed Bug 448007 Opened 16 years ago Closed 2 years ago

[FIX] Make nsEventDispatcher.cpp useable from non-main thread

Categories

(Core :: DOM: Events, defect)

x86
All
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: smaug, Unassigned)

References

Details

Attachments

(1 file, 1 obsolete file)

The idea is to use the event target chain pool (which is an optimization) only 
from main-thread.
Attached patch like this (obsolete) — Splinter Review
This makes nsEventTargetChainItem::Create to use |new|
and nsEventTargetChainItem::Destroy to use |delete| when
non-main-thread is used.

Bent, does this fulfill your requirements?

(For some reason hg diff -w doesn't work, with that the patch would have be smaller.)
Attachment #331344 - Flags: superreview?(jonas)
Attachment #331344 - Flags: review?(jonas)
Comment on attachment 331344 [details] [diff] [review]
like this

This'll work great!

However we might want to hold off landing this until we make sure that the rest of the stuff-off-main-thread strategy is working.
Attachment #331344 - Flags: superreview?(jonas)
Attachment #331344 - Flags: superreview+
Attachment #331344 - Flags: review?(jonas)
Attachment #331344 - Flags: review+
Summary: Make nsEventDispatcher.cpp useable from non-main thread → [FIX] Make nsEventDispatcher.cpp useable from non-main thread
Attached patch Updated to tipSplinter Review
I think we should land this now.
Attachment #331344 - Attachment is obsolete: true
Attachment #342329 - Flags: superreview+
Attachment #342329 - Flags: review+
So workers have non-CC-able event implementations? What about
event listener managers?
Or what kind of setup do we have?

This has been fixed elsewhere. All the DOM event dispatching goes through EventDispatcher.

Assignee: bugs → nobody
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: