Skip to content
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

In-memory DB crashes since QT updated to 5.11 #188

Closed
vicencb opened this issue May 27, 2018 · 8 comments
Closed

In-memory DB crashes since QT updated to 5.11 #188

vicencb opened this issue May 27, 2018 · 8 comments
Assignees
Labels
Component-DB Status-Fixed Ticket is resolved. Type-Defect This is BUG!!!

Comments

@vicencb
Copy link

vicencb commented May 27, 2018

Hi!

Brief description of the issue.

rssguard crashes

How to reproduce the bug?

  1. Configure RSS Guard to use in-memory SQLite database
  2. Update QT from 5.10 to 5.11
  3. Update all items

What is the expected result?

Update the feed list and message list with new un-read messages

What actually happened?

Application closed itself

Other information (logs, see Wiki)

[rssguard] CRITICAL: User wanted to update some feeds but all working threads are occupied. (18/27/05 22:25:17)
...
[rssguard] DEBUG: There are some messages to be updated/added to DB. (18/27/05 22:25:17)
[rssguard] WARNING: QSqlDatabasePrivate::database: requested database does not belong to the calling thread. (18/27/05 22:25:17)
[rssguard] FATAL (terminating application): In-memory SQLite database was NOT opened. Delivered error message: 'Driver not loaded Driver not loaded'. (18/27/05 22:25:17)
Aborted (core dumped)

P.D.: In case it matters, running on ARM64

Regards,
  Vicenç.

@martinrotter
Copy link
Owner

Yes, I reproduced the issue, it is related partially to #80 and #114. The whole feed update mechanism is buggy and needs to be rewritten.

That said, RSS Guard is no longer my priority because I changed my workflow and I do not use any RSS reader app anymore. I might fix this in a future, but I cannot guarantee anything. My time is highly limited and RSS Guard would seriously need some code contributors and/or maintainers.

@martinrotter martinrotter added Type-Defect This is BUG!!! Component-DB Status-Accepted I will eventually implement this. labels May 28, 2018
martinrotter pushed a commit that referenced this issue May 28, 2018
@martinrotter
Copy link
Owner

OK, I think I fixed the issue, can you please test development build compiled from 498e85d?

@xmstspider
Copy link

That said, RSS Guard is no longer my priority because I changed my workflow and I do not use any RSS reader app anymore. I might fix this in a future, but I cannot guarantee anything. My time is highly limited and RSS Guard would seriously need some code contributors and/or maintainers.

Could you write a blog on abclinuxu about this? Maybe someone could help you...

@martinrotter
Copy link
Owner

Will do today.

@vicencb
Copy link
Author

vicencb commented May 28, 2018

This issue got fixed, but another one got introduced.
The way to reproduce the new one is:

  1. Tools
  2. Settings
  3. Data storage
  4. Toggle "Use in-memory database as the working database"
  5. OK
  6. Do you want to restart now? No
  7. File
  8. Quit

The result is:

[rssguard] DEBUG: Syncing settings. (18/28/05 19:22:11)
[rssguard] DEBUG: Destroying FormSettings distance. (18/28/05 19:22:14)
[rssguard] DEBUG: Destroying ToolBarEditor instance. (18/28/05 19:22:14)
[rssguard] DEBUG: Destroying ToolBarEditor instance. (18/28/05 19:22:14)
[rssguard] DEBUG: Destroying ToolBarEditor instance. (18/28/05 19:22:14)
[rssguard] DEBUG: Cleaning up resources and saving application state. (18/28/05 19:22:15)
Segmentation fault (core dumped)

Otherwise, the in-memory DB now works fine and (as long as the setting is not changed) it looks pretty stable.

Thanks,
  Vicenç.

@vicencb
Copy link
Author

vicencb commented May 29, 2018

Hi,
just tested 879a0ca and it works fine!
Thank you.

@martinrotter
Copy link
Owner

This issue got fixed, but another one got introduced.
The way to reproduce the new one is:

@vicencb so this regression issue is fixed for you too? Can I close?

@martinrotter martinrotter self-assigned this Jun 13, 2018
@vicencb
Copy link
Author

vicencb commented Jun 13, 2018

Yes, it can be closed. It works great now!

@martinrotter martinrotter added Status-Fixed Ticket is resolved. and removed Status-Accepted I will eventually implement this. labels Jun 14, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component-DB Status-Fixed Ticket is resolved. Type-Defect This is BUG!!!
Projects
None yet
Development

No branches or pull requests

3 participants