Bug 1008664

Summary: [abrt] mysql-workbench-5.2.47-2.fc19: size: Process /usr/libexec/mysql-workbench-bin was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Alan Schmidt <bucky>
Component: mysql-workbenchAssignee: Remi Collet <fedora>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: adam, fedora
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:e9c15cde4369deb1fffd73f8d6f4e3074b443af7
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-17 17:12:56 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Alan Schmidt 2013-09-16 19:33:39 UTC 
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:
mysql-workbench-5.2.47-2.fc19

Additional info:
reporter:       libreport-2.1.7
backtrace_rating: 4
cmdline:        /usr/libexec/mysql-workbench-bin
crash_function: size
executable:     /usr/libexec/mysql-workbench-bin
kernel:         3.10.11-200.fc19.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
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
Comment 1 Alan Schmidt 2013-09-16 19:33:42 UTC 
Created attachment 798400 [details]
File: backtrace
Comment 2 Alan Schmidt 2013-09-16 19:33:44 UTC 
Created attachment 798401 [details]
File: cgroup
Comment 3 Alan Schmidt 2013-09-16 19:33:47 UTC 
Created attachment 798402 [details]
File: core_backtrace
Comment 4 Alan Schmidt 2013-09-16 19:33:49 UTC 
Created attachment 798403 [details]
File: dso_list
Comment 5 Alan Schmidt 2013-09-16 19:33:51 UTC 
Created attachment 798404 [details]
File: environ
Comment 6 Alan Schmidt 2013-09-16 19:33:53 UTC 
Created attachment 798405 [details]
File: limits
Comment 7 Alan Schmidt 2013-09-16 19:33:56 UTC 
Created attachment 798406 [details]
File: maps
Comment 8 Alan Schmidt 2013-09-16 19:33:58 UTC 
Created attachment 798407 [details]
File: open_fds
Comment 9 Alan Schmidt 2013-09-16 19:34:00 UTC 
Created attachment 798408 [details]
File: proc_pid_status
Comment 10 Alan Schmidt 2013-09-16 19:34:02 UTC 
Created attachment 798409 [details]
File: var_log_messages
Comment 11 Adam Stein 2014-03-17 16:55:43 UTC 
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).

reporter:       libreport-2.1.12
backtrace_rating: 4
cmdline:        /usr/libexec/mysql-workbench-bin
crash_function: size
executable:     /usr/libexec/mysql-workbench-bin
kernel:         3.13.6-100.fc19.x86_64
package:        mysql-workbench-5.2.47-2.fc19
reason:         mysql-workbench-bin killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 12 Alan Schmidt 2014-03-17 17:12:44 UTC 
FYI:

Pursuant to:

http://bugs.mysql.com/?id=71177

...upstream has only just recently made a fix which seems to work for me.
Comment 13 Fedora End Of Life 2015-01-09 19:51:58 UTC 
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.
Comment 14 Fedora End Of Life 2015-02-17 17:12:56 UTC 
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
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.