-
Notifications
You must be signed in to change notification settings - Fork 98
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
Memory issue with OPML import #81
Comments
Please provide us the reader.log file. Its location depends on your OS. |
These are the unregular log-entries: 17 Dec 2013 18:29:15,219 INFO com.sismics.reader.core.listener.async.SubscriptionImportAsyncListener.onSubscriptionImport(SubscriptionImportAsyncListener.java:76) OPML import requested event: SubscriptionImportedEvent{user=User{id=8fabbfbf-d9ab-4b3f-b13b-192b46f7f606, username=hannes3120}, importFile=C:\Users\Hannes\AppData\Local\Temp\reader_opml_import6235763280753652676.tmp} ... 17 Dec 2013 18:29:26,616 INFO com.sismics.reader.core.service.FeedService.synchronize(FeedService.java:248) Synchronization done in 324ms ... 17 Dec 2013 18:30:17,675 INFO com.sismics.reader.core.listener.async.SubscriptionImportAsyncListener.importOutline(SubscriptionImportAsyncListener.java:371) Importing outline 20/152 ... and after that it goes on and on and on like: 17 Dec 2013 19:05:25,614 INFO com.sismics.reader.core.service.FeedService.synchronize(FeedService.java:110) Synchronizing feed at URL: http://notepad-plus-plus.org/feed.rss and then the log just stops without any further message regarding any error... |
It seems to be a memory problem. recompile and try again. Feel free to submit a pull request if it works for you. |
The bug is fixed, and a new version has been released (1.3). |
About your initial issue (more feedback), note that you can access the logs from within the application (Cog icon > About), with a filter (on errors for example). |
Since my import pretty much failed each time now (at first at 2/156, then I deleted an abandoned feed and got to 3/156, figured out that my 'complex' folder-structure might be a problem and simplified it and got to 14/156 (1 failed))
I think it's just a pain to not have some sort of feedback from the server other than the number of the feed - and if there is an issue (there sure is one since the server seems to crash every time and I have to kill the process to be able to launch it again).
And I feel like it shouldn't be able for a user to crash the server just with importing feeds...
From what I've seen the parser runs in an endless loop if there is an error in the parsed feed-url - at least it seems like that from the log...
Maybe ask the user after the 3rd failed try to import the feed?
In general more feedback would be pretty awesome since the design is pretty awesome already this would make this already great client more user-friendly...
The text was updated successfully, but these errors were encountered: