-
Notifications
You must be signed in to change notification settings - Fork 73
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
App stuck on loading screen - uses Network & Disk! #130
Comments
I'm aware of the huge use of network and disk, this is due to the database being downloaded locally from the server. I'm working on an alternative method for this, such as pre-buffering data into memory first, otherwise search the server directly. Still needs some long awaited thorough tests for efficiency and reliability before using in production use. |
Thank you for the quick reply! I just think that this is unexpected behavior and thus should be noted in the app description so not to worry users of the app 👌 |
I end up killing it after it runs for a few hours with no apparent progress. It seems to just be broken. |
I'm having the same issue. |
Am introducing an entirely new database structure, which intends to fix this issue, hence the late update. |
I installed the new update a half hour ago. since then my computers been running hot and this is using 50% of my cpu. and its also stuck no initializing please wait. |
I can't seem to reproduce this issue, it's only takes a matter of seconds to load for me. Could you show some screenshots or provide the log.txt so I can see what's going on. |
Just installed the current version of the app and on its first (and subsequent) run(s) it is stuck on the loading screen.
When I investigated the Task Manager I see extreme use of Network and Disk
There's no explanation why either would be used by the app. Is this the intended behavior? Is the app downloading huge payloads of references to servers?
Please make a note about this unexpected behavior in the README and if you can explain why this is going on.
Thank you 🙇
The text was updated successfully, but these errors were encountered: