Status: Untriaged Owner: ---- CC: bre...@chromium.org, js...@chromium.org, sidc...@chromium.org, lafo...@chromium.org, m...@chromium.org Labels: Type-Bug Pri-2 OS-All Area-Misc Size-Medium
New issue 14721 by js...@chromium.org: crash at hunspell::NodeReader::FindWord http://code.google.com/p/chromium/issues/detail?id=14721 Spun off issue 8551. Quite a lot of crashes have been reported in hunspell::NodeReader::FindWord (bdict_reader.cc:214) http://crash/search?query=product:Chrome++hunspell::NodeReader::FindWord&num=50 The actuall crash seems to happen when bdict_data_[node_offset_] is accessed in id_byte() (inlined). There's a DCHECK for node_offset_ < bdict_length_ before that. I guess in a debug build, it'll be triggered. The problem has been present since 1.0.x. In 1.0.x, apparently, id_byte() was not inlined and the top frame is id_byte(). There may be a specific bdict file triggering this. Getting a minidump and trying to debug should identify one(s) with the problem. -- 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 -~----------~----~----~----~------~----~------~--~---
