Re: [webkit-dev] Time out issue (30s) of WebKit layout test [Mac OS]
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 kbal...@webkit.org wrote: I think this is just the default, WebKitTestRunner has a --timeout that should control this if given. If that's not the case than it seems like a bug for me. On the other hand, I don't think run-webkit-tests supports setting custom timeout for a particular test. Correct, neither old-run-webkit-tests nor new-run-webkit-tests supports per-test custom timeouts. new-run-webkit-tests does support the concept of slow tests (i.e., two timeouts), but we generally use this to reduce the default value (i.e., chromium runs with 6 and 12 seconds). As Brady said, the test needs to be redesigned or broken up if it takes that long to run. -- Dirk ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
[webkit-dev] Time out issue (30s) of WebKit layout test [Mac OS]
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 (waitUntilDone notifyDone are used): static const CFTimeInterval waitToDumpWatchdogInterval = 30.0; That is hard code, and no parameter can be accepted to adjust it. There are two time-out settings for one test case, is it possible to use common time-out setting? Would you please help to double check about it? Best Regards! Horky ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] How to run DumpRenderTree on MacOS in Xcode
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 webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
[webkit-dev] JavaScriptCore memory issue
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 developer tool in Chrome. So that's hard to know which statement resumed so huge memory in Safari FireFox. Any suggestion to clarify the root cause? Thanks Best Regards! Horky ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] JavaScriptCore memory issue
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: 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 developer tool in Chrome. So that's hard to know which statement resumed so huge memory in Safari FireFox. clarify the root cause? Thanks Best Regards! Horky ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
