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.

Sign up for GitHub

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

Jump to bottom

Catch file system failures #144

Closed
timfish opened this issue Dec 3, 2018 · 0 comments · Fixed by #194
Closed

Catch file system failures #144

timfish opened this issue Dec 3, 2018 · 0 comments · Fixed by #194

Comments

@timfish
Copy link
Collaborator

timfish commented Dec 3, 2018

We're seeing a couple of failures while handling Electron dump artifacts. I'm guessing maybe over zealous virus scanner:

Error: EBUSY: resource busy or locked, open 'C:\Users\username\AppData\Local\Temp\OurApp Crashes\01692099-317b-4ea7-b6c1-3d5fbee3c3aa.dmp'

Error: ENOENT: no such file or directory, unlink 'C:\Users\username\AppData\Local\Temp\OurApp Crashes\82e067bc-c36e-4093-98c6-d303ee6e08f9.txt'
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix: Electron v6-7 getsentry/sentry-electron
1 participant
@timfish