FS#50035 - [mysql-workbench] random crash

Attached to Project: Community Packages
Opened by C.D. (stophe) - Thursday, 14 July 2016, 08:15 GMT
Last edited by Christian Hesse (eworm) - Wednesday, 20 July 2016, 06:11 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Christian Hesse (eworm)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Crashs

Additional info:
* package version(s) 6.3.7-1 x86_64
* config and/or log files etc.


Steps to reproduce:
Just do some sql requests, and randomly mysql-workbench crashes.
Tried under KDE and openbox, and on my desktop and my laptop : same issues

Downgrade to 6.3.6 from https://archive.archlinux.org/, seems more usuable
This task depends upon

Closed by  Christian Hesse (eworm)
Wednesday, 20 July 2016, 06:11 GMT
Reason for closing:  Duplicate
Additional comments about closing:   FS#49949 
Comment by Christian Hesse (eworm) - Thursday, 14 July 2016, 08:22 GMT
Any more detailed steps to reproduce this?
Crash logs? Dumps?
Comment by Christian Hesse (eworm) - Monday, 18 July 2016, 06:27 GMT
And bonus question: Does gtk2 2.24.30+95+g876b5f7-1 fix this?
Comment by C.D. (stophe) - Monday, 18 July 2016, 06:50 GMT
Hello Christian

Trying to solve problem with WB 6.3.7, I deleted ~/.mysql/workbench :/
So my logs are now from WB 6.3.6.

To reproduce is simple : WB crashes after doing 3 or 4 queries (basic fonctionnality for this software and so very irritating :)
I also note that 6.3.7 always indicates syntax errors in my queries (white cross in red square in left margin) while 6.3.6 does not with the same queries (normal, queries was well formed)

pacman -Q gtk2 returns gtk2 2.24.30-2 on my 2 computers.
Sorry, not tried with gtk 2.24.30+95.
I suppose that this version is in testing ?

Do you have tried with gtk2 2.24.30+95 ?
Comment by C.D. (stophe) - Tuesday, 19 July 2016, 06:33 GMT
Hi,

I also have tried with 6.3.7 compiled with PKGBUILD : same issue :/
Comment by Christian Hesse (eworm) - Tuesday, 19 July 2016, 07:48 GMT
I can not reproduce...
So a crash log is still much appreciated.
Comment by C.D. (stophe) - Tuesday, 19 July 2016, 08:29 GMT
After 6.3.7 installation, I do some queries and crash :)

wb.log :
10:04:51 [ERR][ main]: Can't communicate with gnome-keyring, it's probably not running. Stored passwords will be lost once quit.
10:04:51 [INF][ WBContext]: Parsing application arguments.
10:04:51 [INF][ WBContext]: /usr/bin/mysql-workbench-bin
10:04:51 [INF][ WBContext UI]: Initializing workbench context UI with these values:
base dir: /usr/share/mysql-workbench
plugin path: /usr/lib/mysql-workbench/plugins
struct path: /usr/share/mysql-workbench/grt
module path: /usr/lib/mysql-workbench/modules
library path: /usr/share/mysql-workbench/libraries
user data dir: /home/stophe/.mysql/workbench
open at start:
open type:
run at startup:
run type:
Force SW rendering: No
Force OpenGL: No
quit when done: No
10:04:51 [INF][ WBContext]: WbContext::init
10:04:51 [INF][ WBA]: Looking for extension modules for WBA...
10:04:51 [INF][ WBA]: 0 extension modules found
10:04:51 [WRN][ grt]: /usr/share/mysql-workbench/data/table_templates.xml:21: link 'com.mysql.rdbms.mysql.datatype.timestamp' <object db.SimpleDatatype> key=simpleType could not be resolved
10:04:51 [WRN][ grt]: /usr/share/mysql-workbench/data/table_templates.xml:106: link 'com.mysql.rdbms.mysql.datatype.varchar' <object db.SimpleDatatype> key=simpleType could not be resolved
10:04:51 [WRN][ grt]: /usr/share/mysql-workbench/data/table_templates.xml:229: link 'com.mysql.rdbms.mysql.datatype.int' <object db.SimpleDatatype> key=simpleType could not be resolved
10:04:51 [INF][ WBContext]: System info:
MySQL Workbench Community (GPL) for Linux/Unix version 6.3.7 CE build 1199 (64 bit)
Configuration Directory: /home/stophe/.mysql/workbench
Data Directory: /usr/share/mysql-workbench
Cairo Version: 1.14.6
OS: Linux 4.6.4-1-ARCH
CPU: 4x Intel(R) Core(TM) i3-4130 CPU @ 3.40GHz (3398.140MHz) - 7,63GiB RAM
Fips mode enabled: no

10:05:54 [INF][ SqlEditor]: Opened connection 'Dev' to Percona XtraDB Cluster (GPL), Release rel72.2, Revision 1, WSREP version 25.11, wsrep_25.11 version 5.6.24-72.2-56-log
10:05:54 [INF][ AutoCCache]: Initializing autocompletion cache for Dev
10:05:54 [INF][ column_widths]: Initializing column width cache for Dev
10:24:23 [ERR][ AutoCCache]: Exception while running refresh task: Lost connection to MySQL server during query
10:24:26 [ERR][ AutoCCache]: Exception while running refresh task: Lost connection to MySQL server during query
10:24:32 [ERR][ AutoCCache]: Exception while running refresh task: Lost connection to MySQL server during query
10:24:36 [ERR][ AutoCCache]: Exception caught while updating triggers name cache for link.compteur: SQL logic error or missing database
10:24:36 [ERR][ AutoCCache]: Exception while running refresh task: Lost connection to MySQL server during query
Comment by Christian Hesse (eworm) - Tuesday, 19 July 2016, 21:13 GMT
This is not of huge help...

Ok, now that gtk2 2.24.30+95+g876b5f7-1 is in [extra] please try if it still crashes with all updates installed.

If it does crash please start mysql-workbench from a terminal. You should see a lot more errors than what wb.log told you.
Comment by C.D. (stophe) - Tuesday, 19 July 2016, 21:28 GMT
I have tried on my laptop with new gtk package just before you answered.
I can do queries without crashes, that's good :)
There is still a problem with the "queries checker" that indicates errors in left gutter, while there is not.
Is this possible to have this feature working as on 6.3.6 ?
Can you explain how to have crash report, other than wb.log ?
Thank's
Comment by Christian Hesse (eworm) - Wednesday, 20 July 2016, 06:09 GMT
Looks like this was a gtk2 issue, fixed with gtk2 2.24.30+95+g876b5f7-1. So I will close the task now.

For other issues please open a new task with detailed description.

Loading...