"PhantomJS has crashed" problem when upgrade to PhantomJS 2.1.1

Got problem like

$ bundle exec rake spec:javascript
Running `"/usr/local/bin/phantomjs" "" "/Users/terry/.rbenv/versions/2.2.0/lib/ruby/gems/2.2.0/gems/jasmine-rails-0.12.4/lib/jasmine_rails/../assets/javascripts/jasmine-runner.js" "file:///Users/terry/git/less-site/tmp/jasmine/runner.html?spec="`
Running: file:///Users/terry/git/less-site/tmp/jasmine/runner.html?spec=
Starting...
PhantomJS has crashed. Please read the bug reporting guide at
<http://phantomjs.org/bug-reporting.html> and file a bug report.

Downgrade PhantomJS to 1.9.8 solved the problem.

[jgarber623]

@searls Did a bit more digging in on this one and found the actual problem in my code.

In a particular spec file, I had code similar to:

describe('some bit of functionality', function() {
  it('does a thing.', function() {
    //
  });
});

That empty assertion callback was causing PhantomJS 2.1.1 to crash. It did not crash PhantomJS 1.9.8. The takeaway here is that empty describe callback functions appear to be okay (for now), but empty it callback functions should be avoided.

describe('some bit of functionality', function() {
  // this is okay
});

describe('some bit of functionality', function() {
  it('does a thing.', function() {
    // you're in for bad times
  });
});

I’m not sure if this will solve anyone else’s problems, but it was the root problem in my codebase.

(Hat tip to @ju-Skinner for his help debugging this one.)

[thekindofme]

In my case the issue was resolved by simply adding the missing () to the end of a method call (it was coffeescript).

- expect( @meter.poll ).toBeFalsy
+ expect( @meter.poll ).toBeFalsy()