Bug 1040253

Summary: Process /usr/bin/report-gtk was killed by signal 5 (SIGTRAP)
Product: [Fedora] Fedora Reporter: Mikhail <mikhail.v.gavrilov>
Component: libreportAssignee: Jakub Filak <jfilak>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: abrt-devel-list, dvlasenk, jberan, jfilak, mlichvar, mmilata, rvokal
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/61947a5c9eb2917e20baecf51061a8cf2cff855f
Whiteboard: abrt_hash:725904b1997f54dafffd4e8fd22694a9f1b1ec24
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 10:47:02 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
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
File: var_log_messages none

Description Mikhail 2013-12-11 03:08:56 UTC
Version-Release number of selected component:
libreport-gtk-2.1.9-1.fc20

Additional info:
reporter:       libreport-2.1.9
backtrace_rating: 4
cmdline:        report-gtk -- /var/tmp/abrt/ccpp-2013-12-11-03:36:06-31847
crash_function: g_thread_new
executable:     /usr/bin/report-gtk
kernel:         3.11.10-301.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #2 g_thread_new at gthread.c:840
 #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:2652
 #6 g_bus_get_sync at gdbusconnection.c:7033
 #7 g_daemon_vfs_init at gdaemonvfs.c:297
 #8 g_type_create_instance at gtype.c:1868
 #9 g_object_new_internal at gobject.c:1746
 #12 try_implementation at giomodule.c:759
 #13 _g_io_module_get_default at giomodule.c:858

Comment 1 Mikhail 2013-12-11 03:09:02 UTC
Created attachment 835080 [details]
File: backtrace

Comment 2 Mikhail 2013-12-11 03:09:05 UTC
Created attachment 835082 [details]
File: cgroup

Comment 3 Mikhail 2013-12-11 03:09:07 UTC
Created attachment 835083 [details]
File: core_backtrace

Comment 4 Mikhail 2013-12-11 03:09:09 UTC
Created attachment 835084 [details]
File: dso_list

Comment 5 Mikhail 2013-12-11 03:09:12 UTC
Created attachment 835085 [details]
File: environ

Comment 6 Mikhail 2013-12-11 03:09:14 UTC
Created attachment 835086 [details]
File: limits

Comment 7 Mikhail 2013-12-11 03:09:16 UTC
Created attachment 835087 [details]
File: maps

Comment 8 Mikhail 2013-12-11 03:09:18 UTC
Created attachment 835088 [details]
File: open_fds

Comment 9 Mikhail 2013-12-11 03:09:21 UTC
Created attachment 835089 [details]
File: proc_pid_status

Comment 10 Mikhail 2013-12-11 03:09:23 UTC
Created attachment 835090 [details]
File: var_log_messages

Comment 11 Jakub Filak 2013-12-11 09:48:28 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 12 Mikhail 2013-12-11 19:02:49 UTC
Thanks for explain here why this crash occurs. But much better will be if this problem will catching and Fedora  showed message what user must doing for increasing process limits, or can increase process limits from this dialog GUI. Can you do it, please?

Comment 13 Jakub Filak 2014-11-27 10:59:15 UTC
ABRT can give you some hints: https://github.com/abrt/faf/issues/212

Comment 14 Jaroslav Reznik 2015-03-03 15:19:12 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22

Comment 15 Fedora End Of Life 2016-07-19 10:47:02 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.