RESOLVED INVALID 32643
REGRESSION: fast/profiler/stop-profiling-after-setTimeout.html crashed on the Leopard Commit Bot 
https://bugs.webkit.org/show_bug.cgi?id=32643
Summary REGRESSION: fast/profiler/stop-profiling-after-setTimeout.html crashed on the...
Eric Seidel (no email)
Reported 2009-12-16 17:48:44 PST
fast/profiler/stop-profiling-after-setTimeout.html crashed on the Leopard Commit Bot This is the first time I've seen this crash: https://bugs.webkit.org/show_bug.cgi?id=32617#c5 Crash log attached.
Attachments
crash log (29.83 KB, text/plain)
2009-12-16 17:48 PST, Eric Seidel (no email) 		no flags
Details
second crash log (29.83 KB, text/plain)
2010-01-12 15:01 PST, Eric Seidel (no email) 		no flags
Details
third crash log (29.83 KB, text/plain)
2010-01-12 15:01 PST, Eric Seidel (no email) 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Eric Seidel (no email)
Comment 1 2009-12-16 17:48:58 PST
Created attachment 45029 [details] crash log
Eric Seidel (no email)
Comment 2 2010-01-11 16:14:56 PST
This seems like a recent regression. This happened again just now: https://bugs.webkit.org/show_bug.cgi?id=33434#c4 Flakey tests make the commit-bot sad. :( (Not to mention useless.) This test has been around for a long while: http://trac.webkit.org/log/trunk/LayoutTests/fast/profiler/stop-profiling-after-setTimeout.html I can get the second crash log off the bot, one sec.
Eric Seidel (no email)
Comment 3 2010-01-12 14:58:37 PST
Hit it again! https://bugs.webkit.org/show_bug.cgi?id=33536#c2
Eric Seidel (no email)
Comment 4 2010-01-12 15:01:12 PST
Created attachment 46399 [details] second crash log I could have sworn I already attached this.
Eric Seidel (no email)
Comment 5 2010-01-12 15:01:42 PST
Created attachment 46400 [details] third crash log
Eric Seidel (no email)
Comment 6 2010-01-12 15:06:09 PST
I think this may be the same bug as bug 33490, just crashing different tests.
Joseph Pecoraro
Comment 7 2016-06-06 20:16:38 PDT
Legacy Profiler has been removed. This test no longer exists.
Note You need to log in before you can comment on or make changes to this bug.