Hi Boris, >> Now my problem occurs when the thread enters UI calls, e.g. raises a >> dialog. On the branch, everything works fine whereas on the trunk the >> application deadlocks. > > So the other thread is opening a dialog?
Yes, using the window-watcher, getting a prompter, .... > That does need to happen from the UI thread. I'm surprised it works on > branch > not to do that... Ok, good to know. That means all code, e.g. some async network answere needs to manually dispatch into the UI thread when calling into chrome? I was suspecting that calls from other threads are dispatched to the UI thread automatically when necessary. thanks, -Daniel _______________________________________________ dev-tech-xpcom mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-xpcom
