Bug 607729 - [abrt] NetworkManager-1:0.8.1-0.3.el6: malloc_consolidate: Process /usr/sbin/NetworkManager was killed by signal 11 (SIGSEGV)
Summary: [abrt] NetworkManager-1:0.8.1-0.3.el6: malloc_consolidate: Process /usr/sbin/...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: NetworkManager
Version: 6.0
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Dan Williams
QA Contact: desktop-bugs@redhat.com
URL:
Whiteboard: abrt_hash:7eb2850c9f4727df8bea8270bd1...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-24 16:29 UTC by Zack Cerza
Modified: 2011-06-14 19:59 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-14 19:59:17 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
File: backtrace (38.85 KB, text/plain)
2010-06-24 16:29 UTC, Zack Cerza 		no flags Details
View All

Description Zack Cerza 2010-06-24 16:29:12 UTC 
abrt version: 1.1.4
architecture: x86_64
Attached file: backtrace
cmdline: NetworkManager --pid-file=/var/run/NetworkManager/NetworkManager.pid
component: NetworkManager
crash_function: malloc_consolidate
executable: /usr/sbin/NetworkManager
global_uuid: 7eb2850c9f4727df8bea8270bd10dc86a333ff09
kernel: 2.6.32-33.el6.x86_64
package: NetworkManager-1:0.8.1-0.3.el6
rating: 4
reason: Process /usr/sbin/NetworkManager was killed by signal 11 (SIGSEGV)
release: Red Hat Enterprise Linux Workstation release 6.0 Beta (Santiago)
Comment 1 Zack Cerza 2010-06-24 16:29:14 UTC 
Created attachment 426643 [details]
File: backtrace
Comment 2 Zack Cerza 2010-06-24 16:31:27 UTC 
Not sure what's causing this; I've been doing wireless testing on this machine, but not via NM...
Comment 3 Dan Williams 2010-06-28 18:43:35 UTC 
Ugh, that part of the code is pretty evil, I'll have to check around.  Are you able to reliably trigger it, or it just happened?
Comment 4 Zack Cerza 2010-07-01 19:19:16 UTC 
I see it happen when I run lots of automated wireless driver tests. So far it's happening on one machine.
Comment 9 Dan Williams 2011-06-14 19:59:17 UTC 
We haven't seen this issue upstream for a very long time and RHEL6 already includes the relevant upstream patches for similar issues.
Note You need to log in before you can comment on or make changes to this bug.