-
Notifications
You must be signed in to change notification settings - Fork 22
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
Large Feed (40K) removed - cleanup crashes #64
Comments
whats the error? whats written in the log? |
rssowlnix.ini (changes made - i've also tried 2GB as well.)
starting Rssowlnix error on either Improving Search or Application Performance (both crash individually) As it's optimising, it slows at feed 475, and crashes at 476 of 686 total feeds. I tried to use the Object Manager (as indicated) .log file crash information
Note: I closed, and then re-opened rssowlnix (and then closed it again) |
I did run a defragment using the Object Manager Tool - no change though |
here is a build that attempts to fix the problem in the log. try it and if it does not work paste the new log parts. https://xyrio.github.io/RSSOwlnix-site/tmp/RSSOwlnix-2-7-1-win32.win32.x86_64.zip |
No luck !SESSION 2019-08-09 18:54:16.550 ----------------------------------------------- !ENTRY org.rssowl.ui 1 0 2019-08-09 18:54:17.508 !ENTRY org.rssowl.core 1 0 2019-08-09 18:54:17.901 !ENTRY org.rssowl.ui 4 4 2019-08-09 18:54:52.788 !ENTRY org.rssowl.ui 1 0 2019-08-09 18:54:53.414 !ENTRY org.rssowl.ui 4 4 2019-08-09 18:54:59.354 !ENTRY org.rssowl.ui 1 0 2019-08-09 18:54:59.355 |
how big is your rssowl.db file? |
forgot that i'd over-written the ini file. Allocating additional ram resolved the issue! FYI the db is was about 550MB, after I ran a defrag in the db4o Object Manager tool it dropped to about 250mb. Currently after running the full clean-up i'm down to 200mb I really appreciate your help |
I removed a 40K unread items feed, when it tries to optimise search and feeds it crashes -i've tried to configure additional ram, but no luck. Any ideas on how I can clean this feed up using db4o browser tools?
The text was updated successfully, but these errors were encountered: