Bug 919860 - [abrt] gedit-3.6.2-1.fc18: magazine_chain_pop_head: Process /usr/bin/gedit was killed by signal 11 (SIGSEGV)
Summary: [abrt] gedit-3.6.2-1.fc18: magazine_chain_pop_head: Process /usr/bin/gedit wa...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: gedit
Version: 18
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:40cb33616ea288aef8c6269d0e6...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-03-10 14:23 UTC by James Legg
Modified: 2014-02-05 19:49 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-02-05 19:49:42 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (98.31 KB, text/plain)
2013-03-10 14:23 UTC, James Legg
no flags Details
File: build_ids (5.37 KB, text/plain)
2013-03-10 14:23 UTC, James Legg
no flags Details
File: cgroup (129 bytes, text/plain)
2013-03-10 14:23 UTC, James Legg
no flags Details
File: core_backtrace (6.69 KB, text/plain)
2013-03-10 14:23 UTC, James Legg
no flags Details
File: dso_list (19.43 KB, text/plain)
2013-03-10 14:23 UTC, James Legg
no flags Details
File: environ (1.44 KB, text/plain)
2013-03-10 14:23 UTC, James Legg
no flags Details
File: limits (1.29 KB, text/plain)
2013-03-10 14:23 UTC, James Legg
no flags Details
File: maps (98.55 KB, text/plain)
2013-03-10 14:23 UTC, James Legg
no flags Details
File: open_fds (1.53 KB, text/plain)
2013-03-10 14:23 UTC, James Legg
no flags Details
File: proc_pid_status (941 bytes, text/plain)
2013-03-10 14:23 UTC, James Legg
no flags Details
File: var_log_messages (524 bytes, text/plain)
2013-03-10 14:23 UTC, James Legg
no flags Details

Description James Legg 2013-03-10 14:23:03 UTC
Description of problem:
Gedit sometimes crashes when moving tabs between gedit windows if the Code Assistance plugin is enabled (I have disabled the other plugins). The likelyhood of a crash is increased when more source files are open.

Steps to reproudce:
- Enable the Code Assistance plugin
- Open a large numer of source files in gedit (I tried 22)
- Drag a tab off the gedit window into empty space to create a new window
- If not crashed yet, line up the gedit windows side by side and move tabs between the windows until a crash occurs (it did not take more than a few attempts with 22 files open)

I've built the code assistance plugin myself from git 97ec876195699cb05c2cd65648119f99c4b7a40b.

Version-Release number of selected component:
gedit-3.6.2-1.fc18

Additional info:
backtrace_rating: 4
cmdline:        gedit
crash_function: magazine_chain_pop_head
executable:     /usr/bin/gedit
kernel:         3.8.1-201.fc18.x86_64
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 magazine_chain_pop_head at gslice.c:528
 #1 thread_memory_magazine1_alloc at gslice.c:835
 #2 g_slice_alloc at gslice.c:994
 #3 g_slist_prepend at gslist.c:265
 #4 g_strsplit at gstrfuncs.c:2268
 #5 rsvg_parse_style at rsvg-styles.c:961
 #6 rsvg_parse_style_attrs at rsvg-styles.c:1473
 #7 rsvg_node_set_atts at rsvg-base.c:1952
 #8 rsvg_standard_element_start at rsvg-base.c:283
 #9 rsvg_start_element at rsvg-base.c:647

Potential duplicate: bug 750087

Comment 1 James Legg 2013-03-10 14:23:09 UTC
Created attachment 707910 [details]
File: backtrace

Comment 2 James Legg 2013-03-10 14:23:11 UTC
Created attachment 707911 [details]
File: build_ids

Comment 3 James Legg 2013-03-10 14:23:13 UTC
Created attachment 707912 [details]
File: cgroup

Comment 4 James Legg 2013-03-10 14:23:16 UTC
Created attachment 707913 [details]
File: core_backtrace

Comment 5 James Legg 2013-03-10 14:23:19 UTC
Created attachment 707914 [details]
File: dso_list

Comment 6 James Legg 2013-03-10 14:23:21 UTC
Created attachment 707915 [details]
File: environ

Comment 7 James Legg 2013-03-10 14:23:24 UTC
Created attachment 707916 [details]
File: limits

Comment 8 James Legg 2013-03-10 14:23:28 UTC
Created attachment 707917 [details]
File: maps

Comment 9 James Legg 2013-03-10 14:23:30 UTC
Created attachment 707918 [details]
File: open_fds

Comment 10 James Legg 2013-03-10 14:23:33 UTC
Created attachment 707919 [details]
File: proc_pid_status

Comment 11 James Legg 2013-03-10 14:23:35 UTC
Created attachment 707920 [details]
File: var_log_messages

Comment 12 Fedora End Of Life 2013-12-21 12:02:06 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

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 prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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 to Fedora 18's end of life.

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 13 Fedora End Of Life 2014-02-05 19:49:42 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.


Note You need to log in before you can comment on or make changes to this bug.