NEW 24772
Temporary AtomicStrings are causing churn in the AtomicString hash
https://bugs.webkit.org/show_bug.cgi?id=24772
Summary Temporary AtomicStrings are causing churn in the AtomicString hash
Eric Seidel (no email)
Reported 2009-03-23 22:47:14 PDT
Temporary AtomicStrings are causing churn in the AtomicString hash mike belshe mentioned seeing some problems related to atomicstring hashtable thrashing in Chromium tonight in #webkit. I wanted to file this bug (and attach a possible patch) before I forgot. Mike may already be working on a solution.
Attachments
Attempt at catching AtomicString table thrash (untested) (4.46 KB, patch)
2009-03-23 22:47 PDT, Eric Seidel (no email)
no flags
Eric Seidel (no email)
Comment 1 2009-03-23 22:47:40 PDT
Created attachment 28883 [details] Attempt at catching AtomicString table thrash (untested) WebCore/platform/text/AtomicString.cpp | 54 ++++++++++++++++++++++---------- 1 files changed, 37 insertions(+), 17 deletions(-)
Mike Belshe
Comment 2 2009-03-25 10:16:24 PDT
Two places I saw this in common code: 1) CSSFontSelector.cpp 2) ResourceRequestBase.cpp I filed bug 24485 for the CSSFontSelector issue. I'm still working on the second. The patch you have proposed won't catch this code (I think) from ResourceRequestBase.cpp: return (m_httpHeaderFields.contains("If-Match") || m_httpHeaderFields.contains("If-Modified-Since") || m_httpHeaderFields.contains("If-None-Match") || m_httpHeaderFields.contains("If-Range") || m_httpHeaderFields.contains("If-Unmodified-Since"));
Mike Belshe
Comment 3 2009-03-25 10:17:24 PDT
(In reply to comment #2) > I filed bug 24485 for the CSSFontSelector issue. Whoops - I meant bug 24785
Note You need to log in before you can comment on or make changes to this bug.