You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes when I save a file in Visual Studio, karma just crashes with a -4082 EBUSY. This is currently only happening to me at work, it never happens on my computer at home. Any advice. I pondered on if it was the virsus scan locking up the file or something. Is there a way to force Karma to contine on an error? I opened the test file in notepad and saved it and it also crashed, but it took me really saving quick over and over to get it to crash, with Visual Studio it is just doing common work.. I will check my version at home (when I get home)
Visual Studio Premium 2013
Karma version 0.12.31
node v0.12.2
PhantomJS
The text was updated successfully, but these errors were encountered:
I am at a loss, so I opened the project in VS2012 and I am noticing it does not happen (or has not happened yet). I will look and see if in VS2013 I have some plug in or extension that is causing this. Perhaps some process has the file in VS2013 (resharper, web essential, some devil spawn). This would explain why it does not happen at home, because I have not upgraded to 2013 yet.
Sometimes when I save a file in Visual Studio, karma just crashes with a -4082 EBUSY. This is currently only happening to me at work, it never happens on my computer at home. Any advice. I pondered on if it was the virsus scan locking up the file or something. Is there a way to force Karma to contine on an error? I opened the test file in notepad and saved it and it also crashed, but it took me really saving quick over and over to get it to crash, with Visual Studio it is just doing common work.. I will check my version at home (when I get home)
Visual Studio Premium 2013
Karma version 0.12.31
node v0.12.2
PhantomJS
The text was updated successfully, but these errors were encountered: