Bug 725170 - [abrt] mysql-workbench-5.2.34-1.fc14: Process /usr/bin/mysql-workbench-bin was killed by signal 11 (SIGSEGV)
Summary: [abrt] mysql-workbench-5.2.34-1.fc14: Process /usr/bin/mysql-workbench-bin wa...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: mysql-workbench
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Remi Collet
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:be8b1792248ab9cc54f0743dc3d...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-23 16:45 UTC by Koltar
Modified: 2011-10-04 17:03 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-10-04 17:03:33 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (74.27 KB, text/plain)
2011-07-23 16:45 UTC, Koltar 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Koltar 2011-07-23 16:45:36 UTC 
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 76051 bytes
cmdline: /usr/bin/mysql-workbench-bin
comment: Noticed mysql workbench was on auto-save mode
component: mysql-workbench
Attached file: coredump, 121266176 bytes
crash_function: sigc::internal::trackable_callback_list::remove_callback
executable: /usr/bin/mysql-workbench-bin
kernel: 2.6.35.13-92.fc14.x86_64
package: mysql-workbench-5.2.34-1.fc14
rating: 4
reason: Process /usr/bin/mysql-workbench-bin was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1311482586
uid: 500

How to reproduce
-----
1.did a large search and replace, workbench locked up buzzing the CPU
2.force the workbench to quit
3.re-opened mysql bench, tried to do a search and find but the window would not appear
4.gave up on the find and replace windows, manually edited, opened another connection to mysql and it crashed
Comment 1 Koltar 2011-07-23 16:45:38 UTC 
Created attachment 514876 [details]
File: backtrace
Comment 2 Remi Collet 2011-10-04 17:03:33 UTC 
Not able to reproduce.

As version 5.2.35 is now available, I close this one.
Note You need to log in before you can comment on or make changes to this bug.