Red Hat Bugzilla – Bug 1008664
[abrt] mysql-workbench-5.2.47-2.fc19: size: Process /usr/libexec/mysql-workbench-bin was killed by signal 11 (SIGSEGV)
Last modified: 2015-02-17 12:12:56 EST
Description of problem:
It started off as the usual thing where if you change your default schema, the first query you perform will make MySQL Workbench die.
However, contrary to the USUAL behavior where simply re-launching Workbench will allow you to continue, workbench instead died immediately upon reconnecting.
Retrying several times eventually allowed me to continue as before.
Version-Release number of selected component:
runlevel: N 5
Thread no. 1 (10 frames)
#0 size at /usr/include/c++/4.8.0/bits/basic_string.h:716
#1 compare at /usr/include/c++/4.8.0/bits/basic_string.h:2227
#2 operator< <char, std::char_traits<char>, std::allocator<char> > at /usr/include/c++/4.8.0/bits/basic_string.h:2571
#3 operator() at /usr/include/c++/4.8.0/bits/stl_function.h:235
#4 _M_lower_bound at /usr/include/c++/4.8.0/bits/stl_tree.h:1150
#5 std::_Rb_tree<std::string, std::pair<std::string const, grt::ValueRef>, std::_Select1st<std::pair<std::string const, grt::ValueRef> >, std::less<std::string>, std::allocator<std::pair<std::string const, grt::ValueRef> > >::find at /usr/include/c++/4.8.0/bits/stl_tree.h:1798
#6 find at /usr/include/c++/4.8.0/bits/stl_map.h:836
#7 grt::internal::Dict::get at grtpp_value.cpp:606
#8 get at ../../library/grt/src/grtpp.h:1683
#9 get_app_option at workbench/wb_context.cpp:184
Potential duplicate: bug 770451
Created attachment 798400 [details]
Created attachment 798401 [details]
Created attachment 798402 [details]
Created attachment 798403 [details]
Created attachment 798404 [details]
Created attachment 798405 [details]
Created attachment 798406 [details]
Created attachment 798407 [details]
Created attachment 798408 [details]
Created attachment 798409 [details]
Another user experienced a similar problem:
Started mysql-workbench, which already had saved SQL tabs which it brought back up. Executed the query in one of the tabs. After mysql-workbench, restarted. Haven't had another crash since the initial time I started mysql-workbench (which is the first time it ran since the system was last booted).
reason: mysql-workbench-bin killed by SIGSEGV
runlevel: N 5
...upstream has only just recently made a fix which seems to work for me.
This message is a notice that Fedora 19 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 19. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 19 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.