Updates:
        Cc: stuartmo...@chromium.org ama...@chromium.org

Comment #10 on issue 16675 by j...@chromium.org: Mac test regressions  
20529:20532
http://code.google.com/p/chromium/issues/detail?id=16675

I managed to get some info for LayoutTests/fast/images/favicon-as-image.html
The problem happens for me about 1 in 50 launches of test shell.
(I was never able to repro with a 'refresh'.)

The last few messages before kaboom are:
[37208:2067:386400678971001:INFO:/Volumes/work/chrome/chromium/src/webkit/glue/plugins/plugin_li
st.cc(178)] Loaded plugin list in 227 ms.
Assertion failed: (!(ev->ev_flags & ~EVLIST_ALL)), function event_del, file
/Volumes/work/chrome/chromium/src/third_party/libevent/event.c, line 789.
Program received signal SIGABRT, Aborted.

Here's a stack which gets there:
#0  event_del (ev=0x4790f70) at  
/Volumes/work/chrome/chromium/src/third_party/libevent/event.c:789
#1  0x0023c8da in timeout_process (base=0x4858c00) at
/Volumes/work/chrome/chromium/src/third_party/libevent/event.c:911
#2  0x0023bc60 in event_base_loop (base=0x4858c00, flags=1) at
/Volumes/work/chrome/chromium/src/third_party/libevent/event.c:519
#3  0x0008c519 in base::MessagePumpLibevent::Run (this=0x476e5a0,  
delegate=0xb02ccd98) at
/Volumes/work/chrome/chromium/src/base/message_pump_libevent.cc:253
#4  0x000829e5 in MessageLoop::RunInternal (this=0xb02ccd98) at
/Volumes/work/chrome/chromium/src/base/message_loop.cc:199
#5  0x00082a01 in MessageLoop::RunHandler (this=0xb02ccd98) at
/Volumes/work/chrome/chromium/src/base/message_loop.cc:181
#6  0x00082a8c in MessageLoop::Run (this=0xb02ccd98) at
/Volumes/work/chrome/chromium/src/base/message_loop.cc:155
#7  0x000c58a7 in base::Thread::ThreadMain (this=0x476dec0) at
/Volumes/work/chrome/chromium/src/base/thread.cc:156
#8  0x00098d08 in ThreadFunc (closure=0x476dec0) at
/Volumes/work/chrome/chromium/src/base/platform_thread_posix.cc:26

The assert fired looks like a failsafe (make sure the flags are only values  
we could possibly set for it).  I can't
see how this could fire without it being a generic memory corruption  
problem.
I don't really know if loading the plugin list (the immediately preceding  
message) is relevant but it's worth a
shot, so cc'ing stuart / amanda to revisit this if we force-ignore  
Quicktime in Mac for now (c.f.
crbug.com/18027)


--
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