Closed Bug 766889 Opened 8 years ago Closed 6 years ago
Remove vestigial threading goop from XPConnect
Once bug 755255 lands, there's a lot of easy cleanup work that can be done. A big part of this is the removal of the map locks, which should give us a free performance boost. At the moment I'm guessing I can do it all in one patch stack, but I may split something off if it turns out that there's a bigger task in there somewhere.
The only thing I really see left to do here is to remove a few threadsafe things from XPConnect. Andrew, can you think of anything else?
Here are a few things I've come across: - NS_DECL_THREADSAFE_ISUPPORTS - NS_INTERFACE_MAP_END_THREADSAFE - nsXPConnect::FindMainThread() is undefined and unused I'm not really sure what to do with bool ClassIsThreadSafe() GET_IT(THREADSAFE) bool ClassIsMainThreadOnly() GET_IT(MAIN_THREAD_ONLY) in XPCWrappedNativeProto.
(In reply to Andrew McCreight [:mccr8] from comment #3) > I'm not really sure what to do with > bool ClassIsThreadSafe() GET_IT(THREADSAFE) This is unused now. > bool ClassIsMainThreadOnly() GET_IT(MAIN_THREAD_ONLY) I think this and the corresponding check in wrapper reparenting can just go away.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.