-
-
Notifications
You must be signed in to change notification settings - Fork 52
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
Windows leveldb LOCK issues #71
Comments
Windows10 Surface Pro 4 the first error in the console is:
|
OK, my best guess here is that for some reason the require cache works differently on Windows than OSX/Linux, which is leading to the local collection leveldb being opened twice. At the moment we depend on the behaviour that is standard in nodejs where if you require the same file twice in the same process, after the first time you just get an object cached in memory that was loaded at the first require. The only possible way that the local collection could be loaded twice is if this behaviour isn't working on Windows with electron. I'll try making sure we just load the collection once, and store it in the app state, although I'm rather unhappy about doing that as it makes the state unserialisable, which in turn makes it harder to restore the app state on startup. |
This is now fixed on all windows instances I have access to. If anyone experiences it again please open a new issue. Fix should work from v1.0.0beta11 onwards. |
On Linux and OSX, beta9 seems to work pretty well. On my rather paltry windows testing machine however, the app appears to complete the initial loading and presents a search screen, but never returns any results.
When I open the devtools console (Ctrl Shift I or F12), I get an error from leveldb, that the process cannot get a handle on the LOCK file.
I initially thought that this was a problem with the way leveldb constructs the LOCK file path (i.e. with a
/
as opposed to an OS-specific path separator, but after trying to manipulate the path inside a running electron instance I don't think that's true.I'm looking for anyone with a Windows machine (preferably better than my netbook) and some knowledge of levelDB to help debug. If any interested parties could download beta9, run it, and if anything seems off open the console and paste the error here I'd appreciate it.
If anyone can offer any insight into the issue (assuming it is reproducible), that would be even better.
The text was updated successfully, but these errors were encountered: