Thanks to you all.
Sure, it's a very special case! I'll try with your comment.
Best Regards!
Horky
On Jun 30, 2012, at 12:19 AM, Dirk Pranke wrote:
> On Fri, Jun 29, 2012 at 9:00 AM, Balazs Kelemen wrote:
>> I think this is just the default, WebKitTestRunner has a --timeout that
>> should co
Hi,
On Mac OS, if one time-out larger than 30s would be used, --time-out-ms cannot
work well.
According to the run-webkit-tests script, custom Time-Out can be assigned for
each test case. But, unfortunately, below line in LayoutTestControllerMac.mm
blocked the setting if it is larger than 30s
Hi,
I confused for this a minute ago. Put the testing file path to argument, it
will run normally. Refer to step 4 in below link:
http://trac.webkit.org/wiki/Debugging%20DumpRenderTree%20on%20Windows
Best Regards!
Horky
___
webkit-dev mailing list
w
Hi,
Thanks for your quick response!
Best Regards!
On Jun 21, 2012, at 8:32 AM, Filip Pizlo wrote:
> Filing a bug is a good place to start!
>
> https://bugs.webkit.org/show_bug.cgi?id=89622
>
> -F
>
>
>
> On Jun 20, 2012, at 5:28 PM, Horky Chen wrote:
>
&g
Hi,
I found one memory management issue about JSC while testing below website on
Mac OS Lion:
http://bigsword.sinaapp.com/game.html
Chrome only needs about 180MB to load the page, but Safari needs almost 450MB
and FireFox needs about 380MB. I only can check the memory usage with the
develope
5 matches
Mail list logo