Crashes on OSX - v1.9.0

[mackermedia]

I looked through the previous issue here: teampoltergeist/poltergeist#44

I tried adding the Rack middleware to filter out .ttf files, but that didn't work.

I'm using PhantomJS v1.9.0 and seeing:
Capybara::Poltergeist::DeadClient:
PhantomJS client died while processing {"name":"visit","args":["http://127.0.0.1:53387/secret"]}

I'm not sure how to attach the .dmp file via Github issues...

[JamesMGreene]

@mackermedia I'd recommend saving the dump file as a Gist and providing the link to it. Alternatively, just paste it into a comment here within a fenced code block (triple backticks at the start and end).

[mackermedia]

@JamesMGreene Thanks for the suggestion.

Dump gist here: https://gist.github.com/mackermedia/5350861

[ariya]

I thought I already fixed all this, see issue #10690.

Can you double check that there is no older version of PhantomJS in the system? phantomjs -v should tell the version.

Also, try to go back to 1.8.2 and see if the crash still persists.

[mackermedia]

FYI: I did phantomjs -v and the result is: 1.9.0.

I did some more debugging and did find that there was a JavaScript error on the page that was making PhatomJS crash. I removed the failure, and it's now working fine. I am using PhantomJS with Poltergeist and have it set to :js_errors => false.

[JamesMGreene]

Thanks for the clarifying.

[mackermedia]

So is the intended behavior for PhantomJS to crash when there is JS error on the page? Or is it an error with poltergeist?

I'm just trying to get more understanding.

[JamesMGreene]

I'm not positive if it should crash (@ariya?) but it should definitely at least report an error to stderr/console.error and exit with an error status.

These are easily handled by adding an appropriate error handler at either the WebPage level, the PhantomJS outer context level, or both.

[mackermedia]

@JamesMGreene Thanks for pointing out those places for JS error handling. That should come in handy.

As for the crashing, just wanted to make sure you guys were aware that it did in fact spit out the error message that PhantomJS died and suggested creating an issue.

[ariya]

I am confused now. If the crash isn't because of TTF font, then please tweak the issue. Narrowing down the issue is also necessary in particular since this is triggered via Poltergeist.

[mackermedia]

Sorry about that. I'm not sure what steps I was using to reliably recreate this error. I've managed to work around it. I don't know if any of the dump information provided is valuable or not.