Problem solved. Didn't call the UI thread through a proxy from the 
communication background thread. Now with the proxy it works like a charm.

Thanks

----- Original Message ----- 
From: "Georg Kalus" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Sunday, August 19, 2007 6:51 PM
Subject: nsIWebNavigation.addTab freezes Firefox?


> Hi group,
>
> I am stuck with this problem for a couple of days now and I am running out 
> of ideas:
>
> Background:
> We have an extension consisting mostly of a XPCOM component written in JS. 
> One of the things we want to do is to synchronize multiple browsers, so 
> that if one user navigates to a new URL, the same URL is opened in all 
> connected browsers.
> The network communication code is written in Java. Because of that we 
> introduced a thin XPCOM component written in C++, that serves as a proxy 
> for the Java code using JNI. The Java communication code is multithreaded.
>
> The problem:
> When a client receives a message from a connected browser, the receiving 
> Java code passes the message to the CPP wrapper XPCOM component, which in 
> turn calls the JS XPCOM component. This works well as long as the JS does 
> simple things like logging to the JS Console. However the browser 
> consistently freezes in nsIWebNavigation.loadURI.
> The calls JS <-> CPP <-> Java work very well if the Java code is 
> single-threaded, so my assumption is that the hang has something to do 
> with threading issues.
>
> Is there anything I have to take care of with loadURI? Anything else I 
> have overlooked? I am very new to Firefox development, so any help is 
> appreciated.
>
> Thanks
> _______________________________________________
> dev-tech-xpcom mailing list
> [email protected]
> https://lists.mozilla.org/listinfo/dev-tech-xpcom
>
> 

_______________________________________________
dev-tech-xpcom mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-xpcom

Reply via email to