I seem to be getting random failures when running run-webkit-tests. I'm not sure if they are related to any changes I've made or not... I see this one most often: running css1/conformance/forward_compatible_parsing test -> failed which I originally attributed to using Bison 2.0... http://bugzilla.opendarwin.org/show_bug.cgi?id=3885 but it doesn't always fail there. I've seen others: running editing/deleting/delete-3928305-fix test -> failed running editing/deleting/delete-and-undo test -> failed running editing/deleting/delete-3608445-fix test -> failed each time it seems to be a crap shoot as to whether it will succeed or fail at some random test. Cosmic rays? Cryo, bdash and Altha on #webkit are seeing similar issues. About half the time all tests succeed, half the time one of them fails. I've tried rolling out: http://bugzilla.opendarwin.org/show_bug.cgi?id=3882 http://bugzilla.opendarwin.org/show_bug.cgi?id=3829 neither helped. Those are the only fixes I made today which I thought could relate to these crashes at all. Again, I have determined (and bdash has confirmed) that neither is related. Off to bed now. I'm not much use to anyone at this hour. -eric p.s. it is remotely possible that either: http://bugzilla.opendarwin.org/show_bug.cgi?id=3826 or http://bugzilla.opendarwin.org/show_bug.cgi?id=3674 are at fault. Neither seems likely. One guess is that this could be an uncaught error in HashSet?? It seems like some sort of memory smasher since it's so random.
On 7/07/2005, at 22:17 , Eric Seidel wrote:
I seem to be getting random failures when running run-webkit-tests. [..] I've tried rolling out: http://bugzilla.opendarwin.org/show_bug.cgi?id=3882 http://bugzilla.opendarwin.org/show_bug.cgi?id=3829 neither helped. [..] p.s. it is remotely possible that either: http://bugzilla.opendarwin.org/show_bug.cgi?id=3826 or http://bugzilla.opendarwin.org/show_bug.cgi?id=3674 are at fault. Neither seems likely.
One guess is that this could be an uncaught error in HashSet?? It seems like some sort of memory smasher since it's so random.
I've spent the last two hours trying to track down which change causes the test failures + DumpRenderTree crash. As was mentioned, rolling out the patch for bugs #3882 and #3829 does not resolve the issue. Rolling out #3826 and #3674 individually didn't help either. It seemed that removing *both* stopped the crashing but that may have just been luck as the crashes are intermittent at best. I'm retesting this scenario now. The crash report is identical each time, but it can take up to six or eight runs of the layout tests for the crash to occur. Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000000 Thread 0 Crashed: 0 <<00000000>> 0xffff8a60 __memcpy + 704 (cpu_capabilities.h:189) 1 com.apple.WebCore 0x0103db00 KWQStringData::initialize (QChar const*, unsigned) + 144 (icplusplus.c:28) 2 com.apple.WebCore 0x01079f64 DOM::DOMString::string() const + 72 (icplusplus.c:28) 3 com.apple.WebCore 0x010d2f18 khtml::HTMLTokenizer::notifyFinished(khtml::CachedObject*) + 280 (icplusplus.c:28) 4 com.apple.WebCore 0x010d3f3c khtml::HTMLTokenizer::scriptHandler() + 452 (icplusplus.c:28) 5 com.apple.WebCore 0x010d4128 khtml::HTMLTokenizer::parseSpecial(khtml::TokenizerString&) + 76 (icplusplus.c:28) 6 com.apple.WebCore 0x010d55b8 khtml::HTMLTokenizer::parseTag(khtml::TokenizerString&) + 4184 (icplusplus.c:28) 7 com.apple.WebCore 0x010d5a40 khtml::HTMLTokenizer::write(khtml::TokenizerString const&, bool) + 868 (icplusplus.c:28) 8 com.apple.WebCore 0x0105c488 KHTMLPart::write(char const*, int) + 628 (icplusplus.c:28) 9 com.apple.WebKit 0x0022f37c -[WebDataSource (WebPrivate) _receivedData:] + 108 (WebDataSource.m:819) 10 com.apple.WebKit 0x0024e38c -[WebMainResourceLoader addData:] + 88 (WebMainResourceLoader.m:156) 11 com.apple.WebKit 0x0022bea4 -[WebLoader didReceiveData:lengthReceived:] + 68 (WebLoader.m:530) 12 com.apple.WebKit 0x0024ed20 -[WebMainResourceLoader didReceiveData:lengthReceived:] + 140 (WebMainResourceLoader.m:367) 13 com.apple.WebKit 0x0022c394 -[WebLoader connection:didReceiveData:lengthReceived:] + 64 (WebLoader.m:633) 14 com.apple.Foundation 0x928ae8a0 -[NSURLConnection (NSURLConnectionInternal) _sendDidReceiveDataCallback] + 564 15 com.apple.Foundation 0x928acd14 -[NSURLConnection (NSURLConnectionInternal) _sendCallbacks] + 440 16 com.apple.Foundation 0x928acae0 _sendCallbacks + 156 17 com.apple.CoreFoundation 0x9074ae2c __CFRunLoopDoSources0 + 384 18 com.apple.CoreFoundation 0x9074a35c __CFRunLoopRun + 452 19 com.apple.CoreFoundation 0x90749ddc CFRunLoopRunSpecific + 268 20 com.apple.Foundation 0x9288b244 -[NSRunLoop runMode:beforeDate:] + 172 21 DumpRenderTree 0x00002f5c dumpRenderTree + 440 (DumpRenderTree.m:248) 22 DumpRenderTree 0x0000325c main + 712 (DumpRenderTree.m:96) 23 DumpRenderTree 0x00002190 _start + 344 (crt.c:272) 24 DumpRenderTree 0x00002034 start + 60 Hopefully someone has more luck tracking this down than I've had. Regards, Mark Rowe <http://bdash.net.nz/>
On 8/07/2005, at 00:41 , Mark Rowe wrote:
I've spent the last two hours trying to track down which change causes the test failures + DumpRenderTree crash. As was mentioned, rolling out the patch for bugs #3882 and #3829 does not resolve the issue. Rolling out #3826 and #3674 individually didn't help either. It seemed that removing *both* stopped the crashing but that may have just been luck as the crashes are intermittent at best. I'm retesting this scenario now.
It seems I was just lucky... As far as I can tell none of the four patches have any relation to the failing test + crash. I'm not sure which other changes have been committed recently that I could check, so I'll leave that up to someone else. Regards, Mark Rowe <http://bdash.net.nz/>
participants (2)
-
Eric Seidel
-
Mark Rowe