-
Notifications
You must be signed in to change notification settings - Fork 55
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
Nw.js integration - Application Killed On Reader Disconnect #9
Comments
Hi @boris-savic, Thank you for posting your issue. I am using this library in Electron (under Windows 10) and it works well (even on reader disconnect – previously is caused errors but they are fixed now). Checklist:
I will let you know once I find out more. |
@VojtechStep Please can you look at it? Thank you. |
Hi, OS: Windows 10 (latest updates) |
I'll take a look at it during this weekend |
Any update on the issue? |
Not yet, I'll have a look at it as soon as I have some time |
Hello, any progress? Can I provide any more useful information? |
Fixed with nwjs 0.23.0... |
@boris-savic, @Klemen1337 so can I close this issue? |
Same bug for the Electron. |
Hi pokusew,
we're trying to fix the issue that happens in Windows environment under NW.js framework. The library works great, but if the reader is physically removed from the computer the application closes without errors.
With some tinkering around I managed to get the Chromium dump file
It seems that on reader disconnect library tries to perform NULL pointer write operation which force closes the whole application. I can't seem to figure out which part of the code does that?
Bests,
Boris
The text was updated successfully, but these errors were encountered: