Bug 1046696 - [abrt] glob2: operator new(): glob2 killed by SIGABRT
Summary: [abrt] glob2: operator new(): glob2 killed by SIGABRT
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: glob2
Version: 19
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Bruno Wolff III
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:4ff7ed5a04a89f65cc7a45cb22a...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-26 15:40 UTC by Brian Benson
Modified: 2015-02-17 19:47 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-02-17 19:47:27 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (15.14 KB, text/plain)
2013-12-26 15:40 UTC, Brian Benson
no flags Details
File: cgroup (154 bytes, text/plain)
2013-12-26 15:40 UTC, Brian Benson
no flags Details
File: core_backtrace (5.10 KB, text/plain)
2013-12-26 15:40 UTC, Brian Benson
no flags Details
File: dso_list (3.17 KB, text/plain)
2013-12-26 15:40 UTC, Brian Benson
no flags Details
File: environ (1.36 KB, text/plain)
2013-12-26 15:40 UTC, Brian Benson
no flags Details
File: limits (1.29 KB, text/plain)
2013-12-26 15:40 UTC, Brian Benson
no flags Details
File: maps (5.00 MB, text/plain)
2013-12-26 15:41 UTC, Brian Benson
no flags Details
File: open_fds (176 bytes, text/plain)
2013-12-26 15:41 UTC, Brian Benson
no flags Details
File: proc_pid_status (930 bytes, text/plain)
2013-12-26 15:41 UTC, Brian Benson
no flags Details

Description Brian Benson 2013-12-26 15:40:45 UTC
Description of problem:
I simply clicked the program icon within my menu.  From there, my computer seemed to slow down considerably.  I looked around and noticed through an applet I have running that the iowait was hitting 200+% and my computer was near unusable.  I was not able to see anything beyond that, as ABRT soon popped up.

Version-Release number of selected component:
glob2-0.9.4.4-18.fc19

Additional info:
reporter:       libreport-2.1.10
backtrace_rating: 4
cmdline:        glob2
crash_function: operator new
executable:     /usr/bin/glob2
kernel:         3.12.5-200.fc19.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000
var_log_messages: Dec 26 10:33:15 gonzo abrt-hook-ccpp[14670]: Saved core dump of pid 14315 (/usr/bin/glob2) to /var/tmp/abrt/ccpp-2013-12-26-10:31:03-14315 (8838750208 bytes)

Truncated backtrace:
Thread no. 1 (10 frames)
 #6 operator new at ../../../../libstdc++-v3/libsupc++/new_op.cc:56
 #7 allocate at /usr/src/debug/gcc-4.8.2-20131212/obj-x86_64-redhat-linux/x86_64-redhat-linux/libstdc++-v3/include/ext/new_allocator.h:104
 #8 std::string::_Rep::_S_create at /usr/src/debug/gcc-4.8.2-20131212/obj-x86_64-redhat-linux/x86_64-redhat-linux/libstdc++-v3/include/bits/basic_string.tcc:607
 #9 std::string::_M_mutate at /usr/src/debug/gcc-4.8.2-20131212/obj-x86_64-redhat-linux/x86_64-redhat-linux/libstdc++-v3/include/bits/basic_string.tcc:479
 #10 std::string::_M_replace_safe at /usr/src/debug/gcc-4.8.2-20131212/obj-x86_64-redhat-linux/x86_64-redhat-linux/libstdc++-v3/include/bits/basic_string.tcc:684
 #11 assign at /usr/include/c++/4.8.0/bits/basic_string.h:1131
 #12 operator= at /usr/include/c++/4.8.0/bits/basic_string.h:555
 #13 Settings::load at src/Settings.cpp:109
 #14 GlobalContainer::GlobalContainer at src/GlobalContainer.cpp:76
 #15 Glob2::run at src/Glob2.cpp:210

Comment 1 Brian Benson 2013-12-26 15:40:49 UTC
Created attachment 841955 [details]
File: backtrace

Comment 2 Brian Benson 2013-12-26 15:40:50 UTC
Created attachment 841956 [details]
File: cgroup

Comment 3 Brian Benson 2013-12-26 15:40:52 UTC
Created attachment 841957 [details]
File: core_backtrace

Comment 4 Brian Benson 2013-12-26 15:40:53 UTC
Created attachment 841958 [details]
File: dso_list

Comment 5 Brian Benson 2013-12-26 15:40:55 UTC
Created attachment 841959 [details]
File: environ

Comment 6 Brian Benson 2013-12-26 15:40:56 UTC
Created attachment 841960 [details]
File: limits

Comment 7 Brian Benson 2013-12-26 15:41:10 UTC
Created attachment 841961 [details]
File: maps

Comment 8 Brian Benson 2013-12-26 15:41:12 UTC
Created attachment 841962 [details]
File: open_fds

Comment 9 Brian Benson 2013-12-26 15:41:13 UTC
Created attachment 841963 [details]
File: proc_pid_status

Comment 10 Fedora End Of Life 2015-01-09 20:57:48 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 11 Fedora End Of Life 2015-02-17 19:47:27 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.


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