Closed HarriBuh closed 3 months ago
Just to get some more details, have you used the "mark as read" or background refresh features?
This may also be related to feed size. How many feeds do you think you have? An OPML file would be helpful but not necessary.
Just to get some more details, have you used the "mark as read" or background refresh features?
This may also be related to feed size. How many feeds do you think you have? An OPML file would be helpful but not necessary.
I've used the "mark below as read" option.
And I think one reason for the crash could indeed be the amount of synched feeds at once. It were about 300+ feeds, as far as I remember. This leads me to another question/ request: Could you implement an option to limit synched feeds by time (e.g. days)? I think your app synched as much feeds as it was able to get in the first start, which definitely is way too much.
I'll try to upload the opml file now.
Thanks for this. I've spent the past few hours digging into the the TransactionTooLargeException. I was able to reproduce by
When you press back, the TransactionTooLargeException
happens. The fix is to rework some of the article data. I have a potential fix (https://github.com/jocmp/capyreader/pull/183) that I'll test again tomorrow (local time).
I have a fix out for this in the latest release, 1010. Please reopen this ticket if you continue to see issues.
Per your other question, I've opened another ticket to investigate ways to cut down on feed refreshes with https://github.com/jocmp/capyreader/issues/185. Thanks again for the thorough bug report!