Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

In Visual Studio, crashed with errno -4082 EBUSY #1397

Closed
maccurt opened this issue May 8, 2015 · 3 comments
Closed

In Visual Studio, crashed with errno -4082 EBUSY #1397

maccurt opened this issue May 8, 2015 · 3 comments

Comments

@maccurt
Copy link

maccurt commented May 8, 2015

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

@maccurt
Copy link
Author

maccurt commented May 8, 2015

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.

@maccurt
Copy link
Author

maccurt commented May 8, 2015

This might shed some light on the issue: codereflection/Giles#40

@maccurt maccurt closed this as completed May 8, 2015
@maccurt
Copy link
Author

maccurt commented May 8, 2015

I closed this issue, because I believe it is a VS2013 issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant