Bug 167622

Summary: [GTK] Performance test IndexedDB/index-get.html deadlocks / timeouts on the GTK+ perf bot.
Product: WebKit Reporter: Carlos Alberto Lopez Perez <clopez>
Component: Tools / TestsAssignee: Nobody <webkit-unassigned>
Status: NEW    
Severity: Normal CC: achristensen, beidson, bugs-noreply, lforschler
Priority: P2    
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
See Also: https://bugs.webkit.org/show_bug.cgi?id=167638
https://bugs.webkit.org/show_bug.cgi?id=167637
https://bugs.webkit.org/show_bug.cgi?id=167640
https://bugs.webkit.org/show_bug.cgi?id=303226
Attachments:
Description Flags
Backtrace from the WebProcess when it has deadlocked
none
Backtrace from the DatabaseProcess when it has deadlocked none

Carlos Alberto Lopez Perez
Reported 2017-01-30 17:41:11 PST
The test IndexedDB/index-get.html timeouts on the GTK+ perf bot since it was added on r209765 <http://trac.webkit.org/r209765>. The test however works fine on my development machine. The only difference I can think of that may explain this is that the GTK+ perf bot has 8GB of RAM, my dev machine 16GB. However, there are no signs of the machine running out of memory or the Linux Kernel OOM killer being triggered. It seems that the test is deadlocking. As soon as it is started on the GTK+ perf bot, the Web and Database process stop using CPU time and remains in that state forever. I have attached a GDB process to the Web and Database process and dumped the stack trace. I'm attaching the traces here. I also tried this patch on the GTK+ perf bot. With it the test works as expected (no longer timeouts): diff --git a/PerformanceTests/IndexedDB/index-get.html b/PerformanceTests/IndexedDB/index-get.html index 89e52673a85..e10aa888fd3 100644 --- a/PerformanceTests/IndexedDB/index-get.html +++ b/PerformanceTests/IndexedDB/index-get.html @@ -36,7 +36,7 @@ function nextStep() testGenerator.next(); } -var numberOfEntries = 5000; +var numberOfEntries = 2000; function *runIteration() {
Attachments
Backtrace from the WebProcess when it has deadlocked (16.25 KB, text/plain)
2017-01-30 17:42 PST, Carlos Alberto Lopez Perez
no flags
Backtrace from the DatabaseProcess when it has deadlocked (13.91 KB, text/plain)
2017-01-30 17:42 PST, Carlos Alberto Lopez Perez
no flags
Carlos Alberto Lopez Perez
Comment 1 2017-01-30 17:42:12 PST
Created attachment 300169 [details] Backtrace from the WebProcess when it has deadlocked
Carlos Alberto Lopez Perez
Comment 2 2017-01-30 17:42:32 PST
Created attachment 300170 [details] Backtrace from the DatabaseProcess when it has deadlocked
Carlos Alberto Lopez Perez
Comment 3 2017-01-31 07:35:50 PST
Note You need to log in before you can comment on or make changes to this bug.