In this bug http://code.google.com/p/chromium/issues/detail?id=28749 It seems we're running afoul of a more finicky compiler not liking some tricks we're playing with objects and memory in LazyInstance. (You can skip down to comment #30 or so to get to the meat of it -- above that point we were still trying to figure out what was causing the crash.)
I know enough to say that it sounds like the solution to the problem should involve placement new, but that is the extent of my C++ skill. If you are a wizard, could you take a look at the patch Craig posted on the bug (http://codereview.chromium.org/519045/show) and comment there?
-- Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev
