Inspector tests started to crash randomly from r144708

• Component: Tools / Tests
• Status: RESOLVED DUPLICATE

[Ádám Kallai]

Some inspector tests started to crash randomly, so I could not really reproduce it. The crashing tests are on Mac and Qt bots. Unfortunately I couldn't check it on GTK port, because all inspector tests are skipped on GTK. Could xou check it please?

For example: 
Mac:

 * inspector/elements/expand-recursively.html
http://build.webkit.org/results/Apple%20Lion%20Release%20WK1%20%28Tests%29/r144716%20%2810010%29/inspector/runtime/runtime-localStorage-getProperties-crash-log.txt

 * inspector/extensions/extensions-reload.html
http://build.webkit.org/results/Apple%20Lion%20Release%20WK1%20%28Tests%29/r144716%20%2810010%29/inspector/extensions/extensions-reload-crash-log.txt

 * inspector/runtime/runtime-localStorage-getProperties.html
http://build.webkit.org/results/Apple%20Lion%20Release%20WK1%20%28Tests%29/r144716%20%2810010%29/inspector/elements/expand-recursively-crash-log.txt

Qt:
 * http/tests/inspector/network/network-request-revision-content.html
http://build.webkit.sed.hu/results/x86-64%20Linux%20Qt%20Release/r144735%20(48823)/http/tests/inspector/resource-tree/resource-tree-events-crash-log.txt
 * http/tests/inspector/resource-tree/resource-tree-events.html
http://build.webkit.sed.hu/results/x86-64%20Linux%20Qt%20Release/r144735%20(48823)/http/tests/inspector/network/network-request-revision-content-crash-log.txt
 * inspector/runtime/runtime-getProperties-isOwnProperty.html
http://build.webkit.sed.hu/results/x86-64%20Linux%20Qt%20Release/r144735%20(48823)/inspector/runtime/runtime-getProperties-isOwnProperty-crash-log.txt
 * inspector/styles/get-set-stylesheet-text.html
http://build.webkit.sed.hu/results/x86-64%20Linux%20Qt%20Release/r144735%20(48823)/inspector/progress-bar-crash-log.txt

[Csaba Osztrogonác]

It seems it is a regression caused by r144708
or a GC or an inspector bug revealed by r144708.

[Alexey Proskuryakov]

<rdar://problem/13348407>

[Andreas Kling]

Rolled out in bug 111447

*** This bug has been marked as a duplicate of bug 111447 ***