On Aug 14, 4:18 am, Zbynek Michl <[email protected]> wrote: > On 14 srp, 02:07, John J Barton <[email protected]> wrote: > > > > > On Aug 13, 4:19 pm, Zbynek Michl <[email protected]> wrote: > > > > Hi there, > > > > I am using background thread in my extension and I am experiencing > > > occasional Firefox hanging when Firebug is installed. When I run my > > > extension or Firebug alone, Firefox works fine. When I omit threading > > > in my code, then Firefox works fine too with both extensions. What > > > could cause that collision? > > > Threading ;-) > > > Javascript in general and the Mozilla runtime in particular are > > designed as event processing systems, not as thread systems. Parts of > > the Mozilla runtime supports multiple threads in the usual sense of > > one UI thread and other threads which never touch the UI. Parts do > > not. In particular jsd, the Javascript debug engine, was written > > before any part of the runtime had threads. > > Hmm, so it is not bug in my/Firebug code, but Mozilla design issue? I > do not touch UI from the background thread, so I am expecting that it > should works correctly.
I can't say for sure. Firebug does not know anything about threads and I hope it never will. I suggest you implement your code as a "plugin" so you can leverage the plugin container technology (multi-process). Process control is a real nuisance but not a mysterious as threads. jjb > > > WebWorkers can be used for background work, they don't have access to > > UI and jsd can't access them. > > Yes, but I need to access my C/C++ component via XPCOM and I am not > sure if I can do that from the WebWorker. > > Zbynek > > > > > > Firefox 3.6.8, Ubuntu 10.04 i686, Firebug 1.5.4 > > > > Thanks, > > > Zbynek -- You received this message because you are subscribed to the Google Groups "Firebug" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/firebug?hl=en.
