I've got a periodic task that can be autostarted when WebKit starts, via a
call to contextInitialize(), or it can be started manually via a web page
being served by WebKit.

When the task is autostarted on WebKit launch, WebKit sometimes slow down
to a dead crawl, as if the task is consuming all the CPU cycles. When I
turn off the autostart, and start the task manually from a web page,
everything seems to be fine. I can't reproduce the problem consistently,
but what I see so far suggests that there is some kind of time-sensitivity
involved, meaning that if the task is kicked of at the wrong moment, it
causes some wierd stall in WebKit.

Can anybody suggest a way for me to isolate the problem? I suppose that if
it is a threading issue (in WebKit--I'm not using threads), then it's going
to be impossible to pin down...?

...Edmund.



-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger 
for complex code. Debugging C/C++ programs can leave you feeling lost and 
disoriented. TotalView can help you find your way. Available on major UNIX 
and Linux platforms. Try it free. www.etnus.com
_______________________________________________
Webware-discuss mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/webware-discuss

Reply via email to