[Webkit-unassigned] [Bug 25421] Threads do not exit or terminate with Safari 4 and Latest Webkit Build

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=25421


mrowe at apple.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mrowe at apple.com




------- Comment #1 from mrowe at apple.com  2009-04-27 13:53 PDT -------
Without knowing exactly what threads are running, I suspect that this is
correct behavior.  Safari, WebKit and other frameworks will start a number of
threads when they are first needed.  When the threads are finished with what
they're doing, they typically just idle on a condition lock or mutex and
consume no CPU time.  This is expected.

Off the top of my thread I can think of a number of such threads:

WebKit icon database
WebKit SQL storage
CFNetwork work thread
CFSocket IO thread
Safari safe browsing thread

Plug-ins, Java in particular, will also create threads that do not necessarily
go away when the page is closed.

In order to understand what these threads are you can attach to Safari using
gdb and run "thread apply all bt" to see backtraces of every thread.  If you
save that output to a text file and attach it here I can check whether there is
anything out of the ordinary.


-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.