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
@@ -36,7 +36,7 @@ function nextStep()
-var numberOfEntries = 5000;
+var numberOfEntries = 2000;
Created attachment 300169 [details]
Backtrace from the WebProcess when it has deadlocked
Created attachment 300170 [details]
Backtrace from the DatabaseProcess when it has deadlocked
This test was skipped for the GTK+ Perf bot in https://trac.webkit.org/changeset/211430/trunk/PerformanceTests/Skipped