Script Error while running Karma start

Hi All,

Let me give the back ground.

Almost around one month back, I used to run 1600 Unit test cases with out any problem. Every thing was working fine.

One fine day, We started getting "Disconnected" error message and at times just place "script error" with unknown reasons so it stopped running the UTC's. So we decided to upgrade the karma from "0.12.16" to the latest one(0.12.28) but that also did not fix the issue. then as next option we upgraded our jasmine from 1.3.0 version to jasmine-2.0\* version and that also did not solve the problem.

To drill down the problem, we decided to put less number of test cases, like just to 50 to find out the problem.

so when I run the unit test cases today, out of running 10 times, 8 times I am getting following error about "script error":

[jenkins@xcclx0000 workspace]$ karma start
INFO [karma]: Karma v0.12.28 server started at http://localhost:9876/
INFO [launcher]: Starting browser PhantomJS
INFO [PhantomJS 1.9.8 (Linux)]: Connected on socket aEsvNiTaam8VX0g4HllC with id 4602773
PhantomJS 1.9.8 (Linux) ERROR
Script error.
PhantomJS 1.9.8 (Linux): Executed 47 of 50 ERROR (0 secs / 3.533 secs)

PhantomJS 1.9.8 (Linux) ERROR
PhantomJS 1.9.8 (Linux): Executed 47 of 50 ERROR (3.549 secs / 3.533 secs)
PhantomJS 1.9.8 (Linux): Executed 47 of 50 ERROR (3.549 secs / 3.533 secs)

Following versions of karma,node and phantomJS I am using:
1. Karma : 0.12.28
2. node : v0.10.28
3. phantomJS: 1.9.8

so I got no idea why this suddenly started failing. It was all good one month back where I was able to run 1600 test cases, now I am unable to run 50 as well.

If you also want to see karma.conf.js content then let me know , I can paste it here.

But please help. Any help will be really great.

Thanks,
Giriraj

Start by reproducing `karma start` with Karma 0.12.28, Node v0.10.28, PhantomJS 1.9.8, and the reduced 50-test run described in the report. Read the Karma configuration when it is provided and compare the failing browser output with the successful runs; done means identifying a reproducible cause for the PhantomJS “Script error” or documenting the missing information needed to proceed.

Written by the indexing model from the issue text.