Phantomjs: console.error() in page JavaScript crashes PhantomJS 2.0

[masi]

When the loaded JS in the web page has a call to console.error() then PhantomJS stops.

console.log() works fine. I didn't test the other console methods.

[japgolly]

This seems like such a quick and easy issue to fix. Is there any chance we could get a 2.0.1 with this fixed sometime soon?

[zackw]

@japgolly We don't even have a release schedule right now :frowning: I can tell you that all the core developers' time is completely tied up with other stuff, like "clean out the bug tracker" :wink: If you have time to fix it yourself and make a pull request, I think we could get it merged quickly, though.

[sjrd]

I see that this bug report has been downgraded to "old.Regression". What does this mean? This is a serious issue for Scala.js users (see https://github.com/scala-js/scala-js/issues/1555).

[zackw]

@sjrd The re-tagging is strictly to do with a reorganization of our bug tracker -- "old" means "old tag scheme." I've updated this bug to the new tag scheme now.

Anyhow, I can't reproduce the problem myself, so it must be something more complicated than just "When the loaded JS in the web page has a call to console.error() then PhantomJS stops." If you can make the bug happen reliably, could we possibly pester you for a reduced test case? Ideally a single .js file that demonstrates the problem when run as phantomjs test.js. You can use the WebServer module to serve a simple webpage that uses console.error.

[masi]

Just for the record, when I use console.error("foobar"); in the main script context the result (Win7, 64bit) is:

foobar

  :0 in error

PhatomJS doesn't crash in this case but there is an unexpected extra output (":0 in error").

[lifeiscontent]

@zackw any updates on this? I'm now getting this in the react_on_rails gem test dummy app

[zackw]

@lifeiscontent As I said last year, we cannot reproduce this problem ourselves, and we need a reduced, self-contained test case. The react_on_rails gem test dummy app is still much too big. We have written some draft bug reporting guidelines which may help you understand what we need - if they are unclear please comment on that over there.

[stale[bot]]

Due to our very limited maintenance capacity (see #14541 for more details), we need to prioritize our development focus on other tasks. Therefore, this issue will be automatically closed. In the future, if we see the need to attend to this issue again, then it will be reopened. Thank you for your contribution!