The build bot shows memory leaks from within JSParser::JSParser at <http://build.webkit.org/results/SnowLeopard%20Intel%20Leaks/r64324%20(9455)/DumpRenderTree7-leaks.txt>. I believe these showed up shortly after the new JavaScript parser was turned on. Oliver said he was going to look at them then but I don’t think a bug was ever filed.
<rdar://problem/8254215>
Is this a bug in ThreadSpecific?
I think that this is a misuse of ThreadSpecific. It can't possibly destroy data for all threads in its own destructor. template<typename T> inline ThreadSpecific<T>::~ThreadSpecific() { pthread_key_delete(m_key); // Does not invoke destructor functions. }
Created attachment 66301 [details] proposed fix
Comment on attachment 66301 [details] proposed fix Clearing flags on attachment: 66301 Committed r66665: <http://trac.webkit.org/changeset/66665>
All reviewed patches have been landed. Closing bug.