Bug 684559

Summary: [abrt] evolution-2.32.2-1.fc14: (SIGSEGV) PR_Lock(NULL), NSS_RegisterShutdown
Product: [Fedora] Fedora Reporter: Jose Rodriguez <jmrbev>
Component: nssAssignee: Elio Maldonado Batiz <emaldona>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: emaldona, kdudka, kengert, lucilanga, mbarnes, mcrha, thierry.vignaud
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:66cd48e9c7ae95b3f855dc722fbd0273b099bd35
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-16 13:10:31 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

Description Jose Rodriguez 2011-03-13 13:02:10 UTC
abrt version: 1.1.17
architecture: i686
Attached file: backtrace, 36642 bytes
cmdline: evolution
component: evolution
Attached file: coredump, 74731520 bytes
crash_function: __pthread_mutex_lock
executable: /usr/bin/evolution
kernel: 2.6.38-0.rc7.git4.1.fc15.i686
package: evolution-2.32.2-1.fc14
rating: 4
reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1300018899
uid: 500

How to reproduce
-----
1. Click on time gnome panel
2. Select task
3. Edit task

Comment 1 Jose Rodriguez 2011-03-13 13:02:14 UTC
Created attachment 483996 [details]
File: backtrace

Comment 2 Milan Crha 2011-03-14 07:45:17 UTC
Thanks for a bug report. I'm moving this to nss because there doesn't seem to be anything we can influence, as this is deep in nss code, unless some memory corruption which I do not suppose happened here.

Thread 1 (Thread 0xb03fcb70 (LWP 3573)):
#0  __pthread_mutex_lock (mutex=0x0) at pthread_mutex_lock.c:50
#1  0x03a9d573 in PR_Lock (lock=0x0) at ../../../mozilla/nsprpub/pr/src/pthreads/ptsynch.c:206
#2  0x004a39a4 in NSS_RegisterShutdown (sFunc=0x6d31d0 <ssl_ShutdownLocks>, appData=0x0) at nssinit.c:896
#3  0x006d31be in initSessionCacheLocksLazily () at sslnonce.c:155
#4  0x03a94813 in PR_CallOnce (once=0x6ecad4, func=0x6d3180 <initSessionCacheLocksLazily>) at ../../../mozilla/nsprpub/pr/src/misc/prinit.c:803
#5  0x006d32ce in ssl_InitSessionCacheLocks (lazyInit=1) at sslnonce.c:175
#6  0x006d331f in lock_cache () at sslnonce.c:190
#7  0x006d35a9 in ssl_LookupSID (addr=0xb6d06cc8, port=57603, peerID=0x0, urlSvrName=0xb6d06270 "imap.gmail.com") at sslnonce.c:278

Comment 3 Elio Maldonado Batiz 2011-09-30 01:11:05 UTC
Jose, have the random crashes with evolution disapeared?

Bug 652630 which is now closed has the same backtrace in attachment 521331 [details] as this one has in attachment 483996 [details] if one concentrates on the calling chain itself.

Comment 4 Fedora End Of Life 2012-08-16 13:10:35 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping