Hi; On Thu, Jul 15, 2010 at 9:58 AM, İsmail Dönmez <[email protected]> wrote:
> Hi again; > > On Wed, Jul 14, 2010 at 8:14 PM, İsmail Dönmez <[email protected]> wrote: > >> Hi Benjamin; >> >> On Wed, Jul 14, 2010 at 8:13 PM, Benjamin Poulain < >> [email protected]> wrote: >>> >>> >>> On 07/14/2010 07:03 PM, ext İsmail Dönmez wrote: >>> >>>> I have a small browser widget based on QWebView using a custom QWebPage. >>>> The app works on an embedded Windows CE device. The problem is if I open >>>> and close the browser 2-3 times no web page will open after the 3th >>>> time. I can reproduce this everytime. Looking at the thread count, >>>> deleting QWebPage leaves some threads around. >>>> >>>> I am guessing these are networking related loader threads. I wonder if >>>> anyone experienced a similar problem before? >>>> >>> >>> It is probably the thread pool. It is cleaned after some time idle. >>> Could you verify if it is the case? >>> >>> >> I indeed suspect so, need to debug further tomorrow in the office. BUT, >> how do I force a cleanup? In embedded space it seems its not cleaned up fast >> enough. >> > > Unfortunately its not the global thread pool, I did; > > QThreadPool::globalInstance()->setExpiryTimeout(500); > > But the threads are still not dying. > My problem doesn't seem to be related to threads living up though. If I create the widget for the 3rd time it won't connect to any website and stuck at 10%. First two times it works fine. Weird. Any ideas appreciated. Regards, ismail
_______________________________________________ webkit-qt mailing list [email protected] http://lists.webkit.org/mailman/listinfo.cgi/webkit-qt
