[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #16715 [Tor Browser]: use ThreadsafeIsCallerChrome() instead of IsCallerChrome()

#16715: use ThreadsafeIsCallerChrome() instead of IsCallerChrome()
-------------------------+-------------------------------------------------
     Reporter:  mcs      |      Owner:  mcs
         Type:  defect   |     Status:  closed
     Priority:  normal   |  Milestone:
    Component:  Tor      |    Version:
  Browser                |   Keywords:  ff38-esr, tbb-5.0,
   Resolution:  fixed    |  TorBrowserTeam201508R
Actual Points:           |  Parent ID:  #14205
       Points:           |
-------------------------+-------------------------------------------------

Comment (by mcs):

 Replying to [comment:5 arthuredelstein]:
 > In the case of #4755 , Kathy's patch has already landed in mozilla-
 central:
 >
 > https://dxr.mozilla.org/mozilla-
 central/rev/d6ea652c579992daa9041cc9718bb7c6abefbc91/dom/events/Event.cpp#889
 >
 > Should we attempt to merge this fix?

 I would say "yes" unless the Mozilla engineers say that
 ThreadsafeIsCallerChrome() is not needed.

 > Is there a situation where an Event object can be accessed from outside
 the main thread?

 I don't know.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/16715#comment:6>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs