<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [ARM] REGRESSION(197226): Removing the on demand executable allocator made 14 tests crash with OOM"
href="https://bugs.webkit.org/show_bug.cgi?id=154822#c5">Comment # 5</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [ARM] REGRESSION(197226): Removing the on demand executable allocator made 14 tests crash with OOM"
href="https://bugs.webkit.org/show_bug.cgi?id=154822">bug 154822</a>
from <span class="vcard"><a class="email" href="mailto:ossy@webkit.org" title="Csaba Osztrogonác <ossy@webkit.org>"> <span class="fn">Csaba Osztrogonác</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=154822#c4">comment #4</a>)
<span class="quote">> Are these just timing out?</span >
No, out of memory because of fixed 16Mb sized VM pool.
I already added my detailed investigation:
(In reply to <a href="show_bug.cgi?id=154822#c3">comment #3</a>)
<span class="quote">> Increasing jitMemoryReservationSize to 32Mb fixes the OOM issue with
> the ARMAssembler (ARM instruction set) and we don't get new crashes.
>
> But with ARMv7Assembler (Thumb2 instruction set) we get ~150 crashes if
> we increase the JIT memory above 16Mb (maximum jump with 24 bit address!)
>
> Zoltán fixed a similar bug in ARMv7Assembler 3 years ago:
> <a href="http://trac.webkit.org/changeset/146396">http://trac.webkit.org/changeset/146396</a></span >
It's easy to fix this bug with ARMAssembler with increasing
jitMemoryReservationSize. But it would cause more problems
with ARMv7Assembler.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>