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
Created attachment 912176 [details] File: backtrace
Created attachment 912177 [details] File: cgroup
Created attachment 912178 [details] File: core_backtrace
Created attachment 912179 [details] File: dso_list
Created attachment 912180 [details] File: environ
Created attachment 912181 [details] File: limits
Created attachment 912182 [details] File: maps
Created attachment 912183 [details] File: open_fds
Created attachment 912184 [details] File: proc_pid_status
Created attachment 912186 [details] File: var_log_messages
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?
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
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
Thanks for reporting back. Feel free to reopen if the problem returns.