CasperJS times out on a page that Chrome can load in much less time. Is this expected?

Vote count:

0

I'm using casperjs 1.1.0-beta3 to measure page load times of a CPU and data intensive web page. In some scenarios, I'm noticing that casper is taking a very long time to detect the test-hook that I have put in place to indicate that the page has finished loading and processing the large amount of data (details of what the hook is and what kind of processing it does it not very relevant, other than to say that the data comes as JSON and the processing is done on the main thread -- no worker threads involved at all).

The issue is, casperjs seems to take a lot more time (10x +) compared to the identical scenario running on regular chrome.

What might be going on? What are some ways to debug?

I have setup casperjs scripts to take a screenshot of the page when it times out, and it shows that the page is still in a 'processing' state. So it indeed looks like the webkit engine used by casper is much slower than normal chrome.

asked 1 min ago

Shyam Habarakada

2,087