mysql-workbench-bin crashed with SIGABRT in __assert_fail_base()

[Philippe Lefevre]

Sudently crashed. No explanation

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: mysql-workbench 5.2.38+dfsg-3
ProcVersionSignature: Ubuntu 3.2.0-55.85-generic 3.2.51
Uname: Linux 3.2.0-55-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
Date: Sat Oct 26 21:06:05 2013
ExecutablePath: /usr/lib/mysql-workbench/bin/mysql-workbench-bin
MarkForUpload: True
ProcCmdline: /usr/lib/mysql-workbench/bin/mysql-workbench-bin
ProcEnviron:
 LANGUAGE=fr_FR:en
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: mysql-workbench
StacktraceTop:
 raise () from /lib/x86_64-linux-gnu/libc.so.6
 abort () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 __assert_fail () from /lib/x86_64-linux-gnu/libc.so.6
 __pthread_mutex_lock_full () from /lib/x86_64-linux-gnu/libpthread.so.0
Title: mysql-workbench-bin crashed with SIGABRT in raise()
UpgradeStatus: Upgraded to precise on 2013-05-30 (149 days ago)
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin mumble-server mysql mythtv netdev plugdev powerdev scanner tape vboxusers video www-data

[Apport retracing service (apport)]

StacktraceTop:
 __assert_fail_base (fmt=<optimized out>, assertion=0x7ff097f3d938 "(-(e)) != 3 || !robust", file=0x7ff097f3df3e "pthread_mutex_lock.c", line=<optimized out>, function=<optimized out>) at assert.c:94
 __GI___assert_fail (assertion=0x7ff097f3d938 "(-(e)) != 3 || !robust", file=0x7ff097f3df3e "pthread_mutex_lock.c", line=312, function=0x7ff097f3da40 <__PRETTY_FUNCTION__.9925> "__pthread_mutex_lock_full") at assert.c:103
 __pthread_mutex_lock_full (mutex=0x7ff09fa22d20) at pthread_mutex_lock.c:312
 ?? ()
 ?? ()

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Rolf Leggewie (r0lf)]

does this ever occur in trusty or later?

[Ed Bessant (ebessant)]

Hello Rolf,

To be quite honest, I had compeletely forgotten about this. As you can
see by the date of my crash report (2013-03-26) this crash happened just
2.5 years ago. I eventually gave up on MythBuntu as a bad joke, and
moved to CentOS. I haven't seen similar crashes in this newer setup,
but I am not even on the same version of Workbench (now 6.0).

I am impressed that you are investigating such an old report, but please
don't feel you have to do so on my behalf.

Thanks,

E.
Ed Bessant

On 18/10/2015 15:34, Rolf Leggewie wrote:
> does this ever occur in trusty or later?
>
> ** Changed in: mysql-workbench (Ubuntu)
> Status: Confirmed => Incomplete
>
> ** Changed in: mysql-workbench (Ubuntu)
> Assignee: (unassigned) => Rolf Leggewie (r0lf)
>

[Rolf Leggewie (r0lf)]

This bug is marked as affecting 6 people. Any of the others still experiencing this? We need to be able to reproduce this or close the ticket.

[Rolf Leggewie (r0lf)]

Too bad. Have to close this as unreproducible. Thank you for reporting.