Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • J jami-client-gnome
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 88
    • Issues 88
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • savoirfairelinux
  • jami-client-gnome
  • Issues
  • #809

Closed
Open
Created Jun 01, 2018 by Hugo Lefeuvre@hlefeuvreDeveloper

database related crash during exit

Sometimes the client crashes during exit with following error messages in the debug output:

** (gnome-ring:31292): DEBUG: quitting
QSqlQuery::prepare: database not open

** (gnome-ring:31292): WARNING **: Can't get conversation at row 0
QSqlQuery::prepare: database not open

** (gnome-ring:31292): WARNING **: Can't get conversation at row 0
QSqlQuery::prepare: database not open
terminate called after throwing an instance of 'lrc::Database::QueryError'
  what():  Driver not loaded Driver not loaded
Aborted (core dumped)

I suspect a race condition in the LRC. Something like:

  1. DB is closed
  2. a signal comes and the callback tries to access the DB's freed data structures

Since this bug is only reproducible on the GNU/Linux GNOME client I'm reporting it here.

How to reproduce:

  1. open a GNU/Linux GNOME client
  2. close it using "quit" button

This crash is pretty rare, and like most race conditions it may not be reproducible on every machine.

Assignee
Assign to
Time tracking