Bug 882953 - [abrt] filezilla-3.5.3-1.fc18.1: g_realloc: Process /usr/bin/filezilla was killed by signal 6 (SIGABRT)
Summary: [abrt] filezilla-3.5.3-1.fc18.1: g_realloc: Process /usr/bin/filezilla was ki...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: filezilla
Version: 18
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Nicolas Chauvet (kwizart)
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:c9cd4600261d806a3169c84faaa...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-12-03 13:09 UTC by Jan Teichmann
Modified: 2013-01-10 09:17 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-01-10 09:17:39 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (68.25 KB, text/plain)
2012-12-03 13:09 UTC, Jan Teichmann 		no flags Details
File: cgroup (126 bytes, text/plain)
2012-12-03 13:09 UTC, Jan Teichmann 		no flags Details
File: core_backtrace (2.88 KB, text/plain)
2012-12-03 13:09 UTC, Jan Teichmann 		no flags Details
File: dso_list (11.90 KB, text/plain)
2012-12-03 13:09 UTC, Jan Teichmann 		no flags Details
File: environ (1.45 KB, text/plain)
2012-12-03 13:09 UTC, Jan Teichmann 		no flags Details
File: limits (1.29 KB, text/plain)
2012-12-03 13:09 UTC, Jan Teichmann 		no flags Details
File: maps (62.66 KB, text/plain)
2012-12-03 13:10 UTC, Jan Teichmann 		no flags Details
File: open_fds (3.59 KB, text/plain)
2012-12-03 13:10 UTC, Jan Teichmann 		no flags Details
File: proc_pid_status (925 bytes, text/plain)
2012-12-03 13:10 UTC, Jan Teichmann 		no flags Details
File: var_log_messages (235 bytes, text/plain)
2012-12-03 13:10 UTC, Jan Teichmann 		no flags Details
View All

Description Jan Teichmann 2012-12-03 13:09:25 UTC 
Version-Release number of selected component:
filezilla-3.5.3-1.fc18.1

Additional info:
backtrace_rating: 4
cmdline:        filezilla
crash_function: g_realloc
executable:     /usr/bin/filezilla
kernel:         3.6.7-5.fc18.x86_64
remote_result:  NOTFOUND
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #7 g_realloc at gmem.c:224
 #8 g_object_weak_ref at gobject.c:2507
 #9 g_object_add_weak_pointer at gobject.c:2586
 #10 gdk_window_queue at gdkgeometry-x11.c:223
 #11 _gdk_x11_window_queue_antiexpose at gdkgeometry-x11.c:258
 #12 gdk_window_process_updates_internal at gdkwindow.c:5606
 #13 gdk_window_process_all_updates at gdkwindow.c:5696
 #14 gdk_window_update_idle at gdkwindow.c:5322
 #20 gtk_main at gtkmain.c:1257
 #21 wxEventLoop::Run at src/gtk/evtloop.cpp:76
Comment 1 Jan Teichmann 2012-12-03 13:09:36 UTC 
Created attachment 656607 [details]
File: backtrace
Comment 2 Jan Teichmann 2012-12-03 13:09:42 UTC 
Created attachment 656608 [details]
File: cgroup
Comment 3 Jan Teichmann 2012-12-03 13:09:45 UTC 
Created attachment 656609 [details]
File: core_backtrace
Comment 4 Jan Teichmann 2012-12-03 13:09:48 UTC 
Created attachment 656610 [details]
File: dso_list
Comment 5 Jan Teichmann 2012-12-03 13:09:52 UTC 
Created attachment 656611 [details]
File: environ
Comment 6 Jan Teichmann 2012-12-03 13:09:55 UTC 
Created attachment 656612 [details]
File: limits
Comment 7 Jan Teichmann 2012-12-03 13:10:01 UTC 
Created attachment 656613 [details]
File: maps
Comment 8 Jan Teichmann 2012-12-03 13:10:05 UTC 
Created attachment 656614 [details]
File: open_fds
Comment 9 Jan Teichmann 2012-12-03 13:10:07 UTC 
Created attachment 656615 [details]
File: proc_pid_status
Comment 10 Jan Teichmann 2012-12-03 13:10:09 UTC 
Created attachment 656616 [details]
File: var_log_messages
Comment 11 Jan Teichmann 2013-01-10 09:17:39 UTC 
I noticed more strange memory corruption in other programs recently and as it turned out I had a defective RAM module. Effects were very random and rare but could be the cause of most memory corruption I lately reported. I assumed it is related to the beta state of F18 so I didnt suspect the RAM at first but MemTest found a small address range with errors.
I am extremely sorry for taking up your time hunting down bugs which are most likely not there. I decided to close my latest bug reports as I can not assure that the memory corruption was actually caused by the program rather than the defect RAM module.
Note You need to log in before you can comment on or make changes to this bug.