Comment #2 on issue 14627 by [email protected]: Crash -  
std::_Rb_tree<std::string, std::pair<std::string const,  
SdchManager::Dictionary*>, std::_Select1st<std::pair<std::string const,  
SdchManager::Dictionary*> >, std::less<std::string>,  
std::allocator<std::pair<std::string const, SdchManager::Dictionary*> >  
>::find(std::string const&)
http://code.google.com/p/chromium/issues/detail?id=14627

Usually a problem in an STL map suggests that there is a threading problem,  
and the
map is being changed on one thread, while being accessed on another.

In this case, the dictionary map is being consulted during the start of a  
filtering
operation, to see if the dictionary referenced in the SDCH encoded content  
is
present. That check (and processing) is done on the IO thread.

The dictionary is updated when an http request returns with a dictionary,  
and that
too is supposed to be on the IO thread.  Hence, it is hard to imagine a  
crash
scenario.

The quoted bug suggests this bug is all the way up at crasher number 25,  
but also
says it has only appeared in only one crash report for one user... which  
makes me a
little skeptical about the crash, and whether it is an actual problem.

I just today (after 189 shipped) enabled SDCH on the mac, and hence it  
should not
even have been active code on a Mac shipped build.

The code around the SDCH filter has not been changing of recent, so it is  
also hard
to suggest a regression in this area, other than generic problems with the  
network
stack, and its recent refactoring.  I'd like to wait-n-see if this shows up
repeatedly before trying to dig much deeper.

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---

Reply via email to