Comment #9 on issue 27644 by [email protected]: Leak in workers http://code.google.com/p/chromium/issues/detail?id=27644
Bah. Looking at it a 3rd time, it looks fine. We're using this idiom: cur_item = iter++; erase(cur_item); So iter should not get invalidated, since it doesn't point at the erased item any longer, and map.erase() doesn't invalidate other iterators: http://stackoverflow.com/questions/52714/stl-vector-vs-map-erase So I'm somewhat stumped. -- 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
