Closed Bug 680714 Opened 13 years ago Closed 12 years ago

Every time when shutting down Seamonkey the Crash report window pops up, but only if Java has been used during the session

Categories

(NSS :: Libraries, defect)

Product:
NSS
Component:
Libraries
Version:
3.12.11
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: petermad, Unassigned)

Details

(Keywords: crash)

Crash Data

User Agent: Mozilla/5.0 (Windows NT 5.1; rv:6.0) Gecko/20110813 Firefox/6.0 SeaMonkey/2.3 Build ID: 20110813174900 Steps to reproduce: I shut down Seamonkey. This ONLY happens if Java (build 1.6.0_26-b03) has been used during the session. It happens since upgrading Seamonkey from 1.1.18 to 2.x - so far I have experienced it with v. 2.2 and 2.3. I only experience it under my Windows XP SP3 installation, not with my Windows 7 x64 SP1 computer. Actual results: The crash report window pops up. Expected results: Seamonkey should just have closed down.
Sorry - it was after upgrading from Seamonkey 2.0.14 and not from 1.1.18 that the bug started to appear.
Please try the following: Uninstall all versions of Java you have in your system. Then install only the latest Java.
Report ID Date Submitted bp-06153ca4-1040-4a99-a4ea-7db05211082021-08-201102:26 bp-05753843-7b7e-45c0-bbd2-7af71211082020-08-201120:18 bp-0b8b3a4f-4da5-4814-8951-1e3c7211082020-08-201120:09 bp-9ad88073-7e20-49e4-8b2e-a94da211081819-08-201101:03 bp-7a252567-a3d8-4a47-b746-238f7211081414-08-201118:42 bp-28206ec8-d88d-4bc7-90ed-9cf40211081414-08-201118:42 bp-48bf72d0-42de-4372-a636-4497f211081414-08-201118:37 bp-cb663f5b-3e9a-4bc8-b79d-04993211081414-08-201118:35 bp-3ebbb698-b5a8-4409-927c-040f3211081414-08-201118:15 bp-48d2382d-49c4-4164-985a-93b25211081414-08-201118:15 bp-64d2e7b5-5cf2-4fb9-920e-cb36b211081414-08-201118:14 bp-28a2a638-a003-46ee-ae57-f2bd3211081414-08-201118:11 bp-62fa0b30-4713-4c4c-8daa-9e687211081414-08-201118:10 bp-f931f33e-57ef-4f3e-b5e2-7645c211081414-08-201117:33 I had already tried uninstalling all Java versions and only installing the latest version prior to reporting this bug
Unfortunately, the crash stacks aren't very informative.
Crash Signature: [_endthread][@0x6a1d81c9]
Keywords: crash
Here are some more crash reports: bp-98763e03-38c8-4116-b74f-e55982110823 23-08-201121:52 bp-776d5688-78cd-4062-92b6-ee0062110823 23-08-201121:51 bp-b1a87790-c5b0-47ac-9051-cd6222110823 23-08-201121:50 bp-07e931da-6d97-49a6-aa21-3f4f12110823 23-08-201121:46 bp-7aa0db8b-aaa4-4f94-beba-d40482110823 23-08-201121:44 bp-9e045414-c7fa-403a-b190-06aee2110823 23-08-201121:44 These are from different URL's that all use Java for access control. Here is one of the URL's that causes Seamonkey to crash at shutdown, if the page has been visited during the browser session: https://www.almbrand.dk/abdk/MitKundeoverblik/index.htm
Thanks. Sorry for the misunderstanding. Your crash reports are all the same. Not your fault that they aren't terribly informative but we don't need any more at the moment.
I now have some more information. The bug dissapears when I unload my Security Device for digitally signing and encrypting emails. This Security Device is issued for the Danish government as an oveall digital signature, and is used for accessing all kinds of websites, like banks and public sites here in Denmark. The Security Device for safe email is connected to the internet site access module where it is driven by Java on the webpages. If I try to use the Security Device for opening encrypted mails the module freezes, and so does SeaMonkey with it. If I unload the Security Device, the site access still works fine, and I don't get the Crash report window anymore when closing down SeaMonkey. I have used the Security Device for a long time with SeaMonkey without problems until I upgraded to v. 2.2. The Security Device still works fine in Mozilla ThundefBird (but I prefer to use SeaMonkey). The Security Device can be optained here: https://www.nemid.nu/support/sikker_e-mail/i_gang_med_sikker_e-mail/hent_program/csp_for_windows/NemID.exe - but you need a NemID certificate to see the bug - If the Security Device is Loaded, but no certificate is installed, the bug don't show. Unfortunately you need to have a Danish social security number to obtain a NemID certificate. See also: https://www.nemid.nu/support/sikker_e-mail/i_gang_med_sikker_e-mail/hent_program/windows/ https://www.nemid.nu/support/sikker_e-mail/i_gang_med_sikker_e-mail/opsaetning_af_e-mail-program/windows_xp/mozilla_thunderbird_3/ The pictures should give you a clue, even if you don't read Danish. Here are some links to new crash reports, that I have obtained playing around with the Security Device in order to try to make it work again - and they are DIFFERENT from the previous crash reports, so mayby they can throw some light over the problem: bp-5b9b39f3-090b-45af-a0aa-088292110904 bp-7fdd6d90-c2e4-4725-aee5-f797c2110904
cc Kaie: does this suggest anything to you? > bp-7fdd6d90-c2e4-4725-aee5-f797c2110904 0 ntdll.dll RtlEnterCriticalSection 1 nspr4.dll PR_Lock nsprpub/pr/src/threads/combined/prulock.c:233 2 nss3.dll PK11_EnterSlotMonitor security/nss/lib/pk11wrap/pk11slot.c:470 3 nss3.dll PK11_IsLoggedIn security/nss/lib/pk11wrap/pk11auth.c:774 4 nss3.dll nssSlot_IsLoggedIn security/nss/lib/pk11wrap/dev3hack.c:314 5 nss3.dll nssToken_IsPrivateKeyAvailable security/nss/lib/dev/devtoken.c:1610 6 nss3.dll NSSCertificate_IsPrivateKeyAvailable security/nss/lib/pki/certificate.c:761 7 nss3.dll pk11ListCertCallback security/nss/lib/pk11wrap/pk11cert.c:2365 8 nss3.dll nssPKIObjectCollection_Traverse security/nss/lib/pki/pkibase.c:938 9 nss3.dll NSSTrustDomain_TraverseCertificates security/nss/lib/pki/trustdomain.c:1084 10 nss3.dll PK11_ListCerts security/nss/lib/pk11wrap/pk11cert.c:2441 11 nss3.dll pk11_keyIDHash_populate security/nss/lib/pk11wrap/pk11cert.c:1570 12 nspr4.dll PR_CallOnceWithArg nsprpub/pr/src/misc/prinit.c:832 13 nss3.dll PK11_FindCertAndKeyByRecipientListNew security/nss/lib/pk11wrap/pk11cert.c:1602 14 smime3.dll NSS_CMSEnvelopedData_Decode_BeforeData security/nss/lib/smime/cmsenvdata.c:350 15 smime3.dll nss_cms_before_data security/nss/lib/smime/cmsdecode.c:248 16 smime3.dll nss_cms_decoder_notify security/nss/lib/smime/cmsdecode.c:198 17 nssutil3.dll sec_asn1d_notify_before security/nss/lib/util/secasn1d.c:451 18 nssutil3.dll sec_asn1d_next_in_sequence security/nss/lib/util/secasn1d.c:2016 19 nssutil3.dll SEC_ASN1DecoderUpdate_Util security/nss/lib/util/secasn1d.c:2668 20 smime3.dll NSS_CMSDecoder_Update security/nss/lib/smime/cmsdecode.c:664 21 xul.dll nsCMSDecoder::Update security/manager/ssl/src/nsCMS.cpp:846 22 xul.dll MimeCMS_write mailnews/mime/src/mimecms.cpp:539 23 xul.dll MimeEncrypted_parse_decoded_buffer mailnews/mime/src/mimecryp.cpp:191 24 xul.dll mime_decode_base64_buffer mailnews/mime/src/mimeenc.cpp:333 25 xul.dll MimeDecoderWrite mailnews/mime/src/mimeenc.cpp:854 26 xul.dll MimeEncrypted_parse_buffer mailnews/mime/src/mimecryp.cpp:170 27 xul.dll MimeMessage_parse_line mailnews/mime/src/mimemsg.cpp:232 28 xul.dll convert_and_send_buffer mailnews/mime/src/mimebuf.cpp:184 29 xul.dll mime_LineBuffer mailnews/mime/src/mimebuf.cpp:272 30 xul.dll MimeObject_parse_buffer mailnews/mime/src/mimeobj.cpp:275 31 xul.dll mime_display_stream_write mailnews/mime/src/mimemoz2.cpp:1011 32 xul.dll nsStreamConverter::OnDataAvailable mailnews/mime/src/nsStreamConverter.cpp:979 33 xul.dll nsDocumentOpenInfo::OnDataAvailable uriloader/base/nsURILoader.cpp:323 34 xul.dll nsMailboxProtocol::ReadMessageResponse mailnews/local/src/nsMailboxProtocol.cpp:586 35 xul.dll nsMailboxProtocol::ProcessProtocolState mailnews/local/src/nsMailboxProtocol.cpp:683 36 xul.dll nsMsgProtocol::OnDataAvailable mailnews/base/util/nsMsgProtocol.cpp:387 37 xul.dll nsInputStreamPump::OnStateTransfer netwerk/base/src/nsInputStreamPump.cpp:510 38 xul.dll nsInputStreamPump::OnInputStreamReady netwerk/base/src/nsInputStreamPump.cpp:400 39 xul.dll nsInputStreamReadyEvent::Run xpcom/io/nsStreamUtils.cpp:114 40 xul.dll nsThread::ProcessNextEvent xpcom/threads/nsThread.cpp:618 41 xul.dll NS_ProcessNextEvent_P objdir/mozilla/xpcom/build/nsThreadUtils.cpp:245 42 xul.dll mozilla::ipc::MessagePump::Run ipc/glue/MessagePump.cpp:110 43 xul.dll MessageLoop::RunInternal ipc/chromium/src/base/message_loop.cc:218 44 xul.dll MessageLoop::RunHandler ipc/chromium/src/base/message_loop.cc:202 45 xul.dll MessageLoop::Run ipc/chromium/src/base/message_loop.cc:176 46 xul.dll nsBaseAppShell::Run widget/src/xpwidgets/nsBaseAppShell.cpp:189 47 xul.dll nsAppShell::Run widget/src/windows/nsAppShell.cpp:249 48 xul.dll nsAppStartup::Run toolkit/components/startup/nsAppStartup.cpp:222 49 xul.dll XRE_main toolkit/xre/nsAppRunner.cpp:3686 50 seamonkey.exe NS_internal_main suite/app/nsSuiteApp.cpp:103 51 seamonkey.exe wmain toolkit/xre/nsWindowsWMain.cpp:106 52 seamonkey.exe __tmainCRTStartup objdir/mozilla/memory/jemalloc/crtsrc/crtexe.c:591 53 kernel32.dll BaseProcessStart
I didn't have the time yet to investigate this crash. Let's switch the bug's component to NSS, as the stack suggests that the crash is inside NSS.
Assignee: nobody → nobody
Component: General → Libraries
Product: SeaMonkey → NSS
QA Contact: general → libraries
Version: SeaMonkey 2.3 Branch → 3.12.11
Peter does this still reproduce for you in current version?
Severity: normal → critical
Flags: needinfo?(petermad)
No, It hasn't happened for quite some time - But whether it is due to changes in SeaMonkey, Java or the Security device I cannot tell - all 3 has been changed.
Flags: needinfo?(petermad)
(In reply to Peter Madsen from comment #13) > No, It hasn't happened for quite some time - But whether it is due to > changes in SeaMonkey, Java or the Security device I cannot tell - all 3 has > been changed. WFM then. Thanks for the update
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.