[Webkit-unassigned] [Bug 174502] [GTK][WPE] stress/dont-reserve-huge-capacity-lexer.js JSC test failing

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=174502

Carlos Alberto Lopez Perez <clopez at igalia.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |lforschler at apple.com

--- Comment #5 from Carlos Alberto Lopez Perez <clopez at igalia.com> ---
(In reply to Zan Dobersek from comment #4)
> > Typical GTK/WPE bots have at least 16GB of RAM available and run 8 tests in
> > parallel. If a test uses [2-4]GB of RAM is fine. If it uses more can be a
> > problem.
> 
> Well obviously 16GB is not enough when a bunch of
> dont-reserve-huge-capacity-lexer.js variations are run together, so as it
> stands this might as well be considered a memory-limited configuration.


How much is enough then? 

Mac bots also have 16GB of RAM and they run on Intel quad-core CPUs with hyper-treading (therefore 4*2 = 8 HW threads => 8 parallel process). And they are not running into issues with the memory usage of the JSC tests.

>From https://build.webkit.org/buildslaves/bot157 I get that the Mac JSC bot has 16GB of RAM and is a Macmini6,2 and from https://en.wikipedia.org/wiki/Mac_Mini#Specifications_2 I translate that model name to an i7-3615QM CPU and http://ark.intel.com/products/64900/Intel-Core-i7-3615QM-Processor-6M-Cache-up-to-3_30-GHz confirms it has 8 threads.


To me this seems to indicate there is a problem somewhere on how JSC handles the memory on Linux ports. I think passing --memory-limit to our bots will only hide this problem instead of fixing it.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20170802/0896e396/attachment.html>