Bug 979779

Summary: [abrt] gnome-abrt-0.2.12-3.fc19: g_thread_new: Process /usr/bin/python2.7 was killed by signal 5 (SIGTRAP)
Product: [Fedora] Fedora Reporter: Sylvain Petreolle <spetreolle>
Component: gnome-abrtAssignee: Jakub Filak <jfilak>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: jberan, jfilak
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:f328065b2066d8512d235eed33f1c74646e67bd6
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-10-14 12:29:27 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status none

Description Sylvain Petreolle 2013-06-30 13:03:14 UTC 
Description of problem:
abrt-gui crashed after I lost my internet connection.

Version-Release number of selected component:
gnome-abrt-0.2.12-3.fc19

Additional info:
reporter:       libreport-2.1.5
backtrace_rating: 4
cmdline:        python /usr/bin/gnome-abrt
crash_function: g_thread_new
executable:     /usr/bin/python2.7
kernel:         3.9.5-301.fc19.x86_64
runlevel:       N 5
uid:            500
var_log_messages: Jun 30 14:13:42 virt abrt[20232]: Saved core dump of pid 20231 (/usr/bin/python2.7) to /var/tmp/abrt/ccpp-2013-06-30-14:13:41-20231 (32362496 bytes)
xsession_errors: 

Truncated backtrace:
Thread no. 1 (10 frames)
 #2 g_thread_new at gthread.c:839
 #3 _g_dbus_shared_thread_ref at gdbusprivate.c:306
 #4 _g_dbus_worker_new at gdbusprivate.c:1680
 #5 initable_init at gdbusconnection.c:2640
 #6 g_bus_get_sync at gdbusconnection.c:6882
 #7 g_daemon_vfs_init at gdaemonvfs.c:297
 #8 g_type_create_instance at gtype.c:1917
 #9 g_object_constructor at gobject.c:1855
 #12 try_implementation at giomodule.c:759
 #13 _g_io_module_get_default at giomodule.c:858
Comment 1 Sylvain Petreolle 2013-06-30 13:03:19 UTC 
Created attachment 767072 [details]
File: backtrace
Comment 2 Sylvain Petreolle 2013-06-30 13:03:22 UTC 
Created attachment 767073 [details]
File: cgroup
Comment 3 Sylvain Petreolle 2013-06-30 13:03:25 UTC 
Created attachment 767074 [details]
File: core_backtrace
Comment 4 Sylvain Petreolle 2013-06-30 13:03:28 UTC 
Created attachment 767075 [details]
File: dso_list
Comment 5 Sylvain Petreolle 2013-06-30 13:03:31 UTC 
Created attachment 767076 [details]
File: environ
Comment 6 Sylvain Petreolle 2013-06-30 13:03:35 UTC 
Created attachment 767077 [details]
File: limits
Comment 7 Sylvain Petreolle 2013-06-30 13:03:38 UTC 
Created attachment 767078 [details]
File: maps
Comment 8 Sylvain Petreolle 2013-06-30 13:03:41 UTC 
Created attachment 767079 [details]
File: open_fds
Comment 9 Sylvain Petreolle 2013-06-30 13:03:44 UTC 
Created attachment 767080 [details]
File: proc_pid_status
Comment 10 Jakub Filak 2013-10-14 12:29:27 UTC 
Thank you for the report. The crash occurred because of insufficient resources to create another thread, or a system-imposed limit on the number of threads was encountered. The latter case may occur in two ways: the RLIMIT_NPROC soft resource limit (set  via  setrlimit(2)),  which  limits  the  number  of  process for a real user ID, was reached; or the kernel's system-wide limit on the number of threads, /proc/sys/kernel/threads-max, was reached. Closing as NOTABUG but, please feel free to report any further bugs you find.
Comment 11 Sylvain Petreolle 2013-10-15 23:34:23 UTC 
Thanks for the feedback.