blink_perf.parser: Reduce how much we recurse
Some of these tests caused blink to recurse to stacks > 4,000 frames deep. This caused crashes for Android on ARM64, which has a standard stack limit of 1MB. Since it appears that these benchmarks' depths are somewhat arbitrary (e.g. the crashes that we're seeing when running these benchmarks aren't indicative of a problem in the real world), turning down the recursion seems reasonable here. New limits were chosen arbitrarily. Bug: 851539 Test: Ran blink_perf.parser on ARM64 Android; no crashes observed. Change-Id: I310b5e92fcb32524ec6e1c8a1c67226d68f4e5aa Reviewed-on: https://chromium-review.googlesource.com/1111685 Commit-Queue: George Burgess <gbiv@chromium.org> Reviewed-by:Kentaro Hara <haraken@chromium.org> Reviewed-by:
Yuki Shiino <yukishiino@chromium.org> Reviewed-by:
Jeremy Roman <jbroman@chromium.org> Cr-Commit-Position: refs/heads/master@{#569720}
Showing
Please register or sign in to comment