Bug 1113229 - [abrt] nxagent: XFree(): nxagent killed by SIGABRT
Summary: [abrt] nxagent: XFree(): nxagent killed by SIGABRT
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: nx-libs
Version: 20
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Orion Poplawski
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:f53fd2d6c1645295a5b4b6452e3...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-06-25 17:06 UTC by Sam
Modified: 2014-07-11 15:49 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-07-11 15:49:40 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (27.70 KB, text/plain)
2014-06-25 17:06 UTC, Sam
no flags Details
File: cgroup (172 bytes, text/plain)
2014-06-25 17:06 UTC, Sam
no flags Details
File: core_backtrace (8.65 KB, text/plain)
2014-06-25 17:06 UTC, Sam
no flags Details
File: dso_list (2.95 KB, text/plain)
2014-06-25 17:06 UTC, Sam
no flags Details
File: environ (1.08 KB, text/plain)
2014-06-25 17:06 UTC, Sam
no flags Details
File: limits (1.29 KB, text/plain)
2014-06-25 17:06 UTC, Sam
no flags Details
File: maps (14.38 KB, text/plain)
2014-06-25 17:06 UTC, Sam
no flags Details
File: open_fds (438 bytes, text/plain)
2014-06-25 17:06 UTC, Sam
no flags Details
File: proc_pid_status (974 bytes, text/plain)
2014-06-25 17:06 UTC, Sam
no flags Details
File: var_log_messages (29 bytes, text/plain)
2014-06-25 17:06 UTC, Sam
no flags Details

Description Sam 2014-06-25 17:06:38 UTC
Version-Release number of selected component:
nxagent-3.5.0.22-1.fc20

Additional info:
reporter:       libreport-2.2.2
backtrace_rating: 4
cmdline:        /usr/lib64/nx/bin/nxagent -persistent -R -name 'NX - sam@server:2000 - 192.168.1.80 (GPL Edition)' -option /home/sam/.nx/C-server-2000-D544EC435105CBAEA1814C5B60B31BA2/options -nolisten tcp :2000
crash_function: XFree
executable:     /usr/lib64/nx/bin/nxagent
kernel:         3.14.6-200.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #5 XFree at XlibInt.c:3732
 #6 _XcmsGetProperty at cmsProp.c:137
 #7 LINEAR_RGB_InitSCCData at LRGB.c:496
 #8 _XcmsInitScrnInfo at cmsInt.c:336
 #9 XcmsDefaultCCC at CCC.c:241
 #10 XcmsCreateCCC at CCC.c:111
 #11 CmapRecForColormap at cmsCmap.c:113
 #12 XcmsCCCOfColormap at cmsCmap.c:433
 #13 XParseColor at ParseCol.c:92
 #14 AllocColor at create.c:247

Comment 1 Sam 2014-06-25 17:06:42 UTC
Created attachment 912176 [details]
File: backtrace

Comment 2 Sam 2014-06-25 17:06:44 UTC
Created attachment 912177 [details]
File: cgroup

Comment 3 Sam 2014-06-25 17:06:45 UTC
Created attachment 912178 [details]
File: core_backtrace

Comment 4 Sam 2014-06-25 17:06:47 UTC
Created attachment 912179 [details]
File: dso_list

Comment 5 Sam 2014-06-25 17:06:49 UTC
Created attachment 912180 [details]
File: environ

Comment 6 Sam 2014-06-25 17:06:51 UTC
Created attachment 912181 [details]
File: limits

Comment 7 Sam 2014-06-25 17:06:53 UTC
Created attachment 912182 [details]
File: maps

Comment 8 Sam 2014-06-25 17:06:55 UTC
Created attachment 912183 [details]
File: open_fds

Comment 9 Sam 2014-06-25 17:06:56 UTC
Created attachment 912184 [details]
File: proc_pid_status

Comment 10 Sam 2014-06-25 17:06:58 UTC
Created attachment 912186 [details]
File: var_log_messages

Comment 11 Orion Poplawski 2014-06-25 18:18:08 UTC
Hmm, looks like some kind of memory corruption - trying to free address 0x48 which is clearly bad.  Will probably need to run nxagent under valgrind to try to find these things.

Is this repeatable?

Comment 12 Sam 2014-06-28 22:46:04 UTC
I am on vacation. I can run nxserver in valgrind when I get home in a little over a week. I have been having random crashing problems particularly with my zfs volumes mounted.

I replaced most of the ram a month ago. I did not run memtest yet. I forgot. 

I have not used valgrind before,  but I will study some before I get back. 

Thank you for the help. 

Sam

Comment 13 Sam 2014-07-11 15:29:10 UTC
I am back from vacation. I replaced the motherboard and processors. So far everything has been running great for a week. I believe the issue is solved. 

It would have taken me a long time to get to a resolution without your help, so Thank You very much for your insight.

Sam

Comment 14 Orion Poplawski 2014-07-11 15:49:40 UTC
Thanks for reporting back.  Feel free to reopen if the problem returns.


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