[JIRA] Created: (SSPCPP-512) Shibboleth Crash/Hang: KERNELBASE!RaiseException, shibsp1_4!shibsp::Handler::preserveRelayState
csowers@idp.protectnetwork.org (JIRA)
noreply at shibboleth.net
Thu Oct 4 11:17:21 EDT 2012
Shibboleth Crash/Hang: KERNELBASE!RaiseException, shibsp1_4!shibsp::Handler::preserveRelayState
-----------------------------------------------------------------------------------------------
Key: SSPCPP-512
URL: https://issues.shibboleth.net/jira/browse/SSPCPP-512
Project: Shibboleth SP - C++
Issue Type: Bug
Affects Versions: 2.4.2
Environment: Windows Server 2008 R2 Service Pack 1
Reporter: csowers at idp.protectnetwork.org
Assignee: Scott Cantor
Priority: Minor
Attachments: shibboleth-dump.mht
Shibboleth is crashing/hanging and creating DMP files, filling up the hard disk. Each DMP is about 35mb. There are about 5 DMP files created each day. I right clicked on one, and selected Analyze Crash/Hang Issue, and it generated this report. Sorry, I don't know what caused it and I don't have much experience with C++ on Windows. I also attached an MHT file which you can open in Internet Explorer. I can analyze other dump files too if you want.
{code}
Analysis Summary
Type Description Recommendation
Error In SHIBD_~2.DMP the assembly instruction at KERNELBASE!RaiseException+58 in C:\Windows\SysWOW64\KERNELBASE.dll from Microsoft Corporation has caused an unknown exception (0xe06d7363) on thread 14
Please follow up with vendor Microsoft Corporation for problem resolution concerning the following file: C:\Windows\SysWOW64\KERNELBASE.dll.
Warning The following threads in SHIBD_~2.DMP are waiting on data to be returned from another server via WinSock.
The call to WinSock originated from shibsp1_4!shibsp::ListenerService::init+14df
( 13 )
6.67% of threads blocked
Ensure that any remote server this application may be calling is functioning properly and there are no network issues between the two servers. If the problem continues, please contact the application vendor for further assistance
Warning The following threads in SHIBD_~2.DMP are waiting on data to be returned from another server via WinSock.
The call to WinSock originated from shibsp1_4!shibsp::ListenerService::init+970
( 3 )
6.67% of threads blocked
Ensure that any remote server this application may be calling is functioning properly and there are no network issues between the two servers. If the problem continues, please contact the application vendor for further assistance
Analysis Details
Your browser settings are currently prohibiting this report's scripts from running.
This is preventing some features of this analysis report from displaying properly. To enable scripts to run, right-click the security warning above and choose "Allow Blocked Content..." or enable the "Allow active content to run in files on My Computer*" setting on the Advanced tab of your "Internet Options" dialog to avoid being prompted in the future
Table Of Contents
SHIBD_~2.DMP
Top 5 threads by CPU time
Thread report
Faulting Module Information
Report for SHIBD_~2.DMP
Report for SHIBD_~2.DMP
Type of Analysis Performed Combined Crash/Hang Analysis
Machine Name CMSNYWEB01
Operating System Windows Server 2008 R2 Service Pack 1
Number Of Processors 4
Process ID 11244
Process Image D:\Packages\shibboleth-sp-2.4.2\sbin\shibd.exe
System Up-Time 11 day(s) 08:41:34
Process Up-Time 00:01:08
Top 5 Threads by CPU time
Note - Times include both user mode and kernel mode for each thread Thread ID: 3 Total CPU Time: 00:00:01.201 Entry Point for Thread: 0x007e37a8
Thread ID: 13 Total CPU Time: 00:00:00.046 Entry Point for Thread: 0x00000000
Thread ID: 14 Total CPU Time: 00:00:00.015 Entry Point for Thread: 0x00000000
Thread ID: 0 Total CPU Time: 00:00:00.015 Entry Point for Thread: 0x00000000
Thread ID: 4 Total CPU Time: 00:00:00.00 Entry Point for Thread: 0x00000000
Thread report
Thread 0 - System ID 15108
Entry point 0x00000000
Create time 10/3/2012 9:00:16 PM
Time spent in user mode 0 Days 00:00:00.015
Time spent in kernel mode 0 Days 00:00:00.00
This thread is not fully resolved and may or may not be a problem. Further analysis of these threads may be required.
Function Source
ntdll!ZwWaitForSingleObject+15
KERNELBASE!WaitForSingleObjectEx+98
kernel32!WaitForSingleObjectExImplementation+75
kernel32!WaitForSingleObject+12
sechost!ScSendResponseReceiveControls+ea
sechost!ScDispatcherLoop+c2
sechost!StartServiceCtrlDispatcherA+68
shibd+14a3
shibd+2e88
kernel32!BaseThreadInitThunk+e
ntdll!__RtlUserThreadStart+70
ntdll!_RtlUserThreadStart+1b
Back to Top
Thread 1 - System ID 1424
Entry point 0x00000000
Create time 10/3/2012 9:00:16 PM
Time spent in user mode 0 Days 00:00:00.00
Time spent in kernel mode 0 Days 00:00:00.00
Function Source
ntdll!ZwWaitForWorkViaWorkerFactory+12
ntdll!TppWorkerThread+216
kernel32!BaseThreadInitThunk+e
ntdll!__RtlUserThreadStart+70
ntdll!_RtlUserThreadStart+1b
Back to Top
Thread 2 - System ID 17232
Entry point 0x00000000
Create time 10/3/2012 9:00:16 PM
Time spent in user mode 0 Days 00:00:00.00
Time spent in kernel mode 0 Days 00:00:00.00
Function Source
ntdll!ZwWaitForWorkViaWorkerFactory+12
ntdll!TppWorkerThread+216
kernel32!BaseThreadInitThunk+e
ntdll!__RtlUserThreadStart+70
ntdll!_RtlUserThreadStart+1b
Back to Top
Thread 3 - System ID 14164
Entry point 0x007e37a8
Create time 10/3/2012 9:00:16 PM
Time spent in user mode 0 Days 00:00:01.045
Time spent in kernel mode 0 Days 00:00:00.156
This thread is waiting on data to be returned from another server via WinSock.
The call to WinSock originated from shibsp1_4!shibsp::ListenerService::init+970
Function Source
ntdll!ZwWaitForSingleObject+15
mswsock!SockWaitForSingleObject+1ba
mswsock!WSPSelect+3a6
ws2_32!select+494
shibsp1_4!shibsp::ListenerService::init+970
shibd+114d
shibd+151e
sechost!ScSvcctrlThreadW+21
kernel32!BaseThreadInitThunk+e
ntdll!__RtlUserThreadStart+70
ntdll!_RtlUserThreadStart+1b
Back to Top
Thread 4 - System ID 16936
Entry point 0x00000000
Create time 10/3/2012 9:00:16 PM
Time spent in user mode 0 Days 00:00:00.00
Time spent in kernel mode 0 Days 00:00:00.00
Function Source
ntdll!NtWaitForMultipleObjects+15
ntdll!TppWaiterpThread+33d
kernel32!BaseThreadInitThunk+e
ntdll!__RtlUserThreadStart+70
ntdll!_RtlUserThreadStart+1b
Back to Top
Thread 5 - System ID 3200
Entry point 0x00000000
Create time 10/3/2012 9:00:17 PM
Time spent in user mode 0 Days 00:00:00.00
Time spent in kernel mode 0 Days 00:00:00.00
This thread is not fully resolved and may or may not be a problem. Further analysis of these threads may be required.
Function Source
ntdll!ZwWaitForSingleObject+15
KERNELBASE!WaitForSingleObjectEx+98
kernel32!WaitForSingleObjectExImplementation+75
kernel32!WaitForSingleObject+12
xmltooling1_4!xmltooling::URLEncoder::isBad+730
xmltooling1_4!xmltooling::URLEncoder::isBad+5b0
xmltooling1_4!xmltooling::ReloadableXMLFile::reload_fn+161
kernel32!BaseThreadInitThunk+e
ntdll!__RtlUserThreadStart+70
ntdll!_RtlUserThreadStart+1b
Back to Top
Thread 6 - System ID 12908
Entry point 0x00000000
Create time 10/3/2012 9:00:17 PM
Time spent in user mode 0 Days 00:00:00.00
Time spent in kernel mode 0 Days 00:00:00.00
This thread is not fully resolved and may or may not be a problem. Further analysis of these threads may be required.
Function Source
ntdll!ZwWaitForSingleObject+15
KERNELBASE!WaitForSingleObjectEx+98
kernel32!WaitForSingleObjectExImplementation+75
kernel32!WaitForSingleObject+12
xmltooling1_4!xmltooling::URLEncoder::isBad+730
xmltooling1_4!xmltooling::AnyElementBuilder::buildObject+d2f
kernel32!BaseThreadInitThunk+e
ntdll!__RtlUserThreadStart+70
ntdll!_RtlUserThreadStart+1b
Back to Top
Thread 7 - System ID 10460
Entry point 0x00000000
Create time 10/3/2012 9:00:17 PM
Time spent in user mode 0 Days 00:00:00.00
Time spent in kernel mode 0 Days 00:00:00.00
This thread is not fully resolved and may or may not be a problem. Further analysis of these threads may be required.
Function Source
ntdll!ZwWaitForSingleObject+15
KERNELBASE!WaitForSingleObjectEx+98
kernel32!WaitForSingleObjectExImplementation+75
kernel32!WaitForSingleObject+12
xmltooling1_4!xmltooling::URLEncoder::isBad+730
xmltooling1_4!xmltooling::URLEncoder::isBad+5b0
xmltooling1_4!xmltooling::ReloadableXMLFile::reload_fn+161
kernel32!BaseThreadInitThunk+e
ntdll!__RtlUserThreadStart+70
ntdll!_RtlUserThreadStart+1b
Back to Top
Thread 8 - System ID 10684
Entry point 0x00000000
Create time 10/3/2012 9:00:19 PM
Time spent in user mode 0 Days 00:00:00.00
Time spent in kernel mode 0 Days 00:00:00.00
Function Source
ntdll!NtRemoveIoCompletion+15
mswsock!SockAsyncThread+83
kernel32!BaseThreadInitThunk+e
ntdll!__RtlUserThreadStart+70
ntdll!_RtlUserThreadStart+1b
Back to Top
Thread 9 - System ID 11020
Entry point 0x00000000
Create time 10/3/2012 9:00:20 PM
Time spent in user mode 0 Days 00:00:00.00
Time spent in kernel mode 0 Days 00:00:00.00
This thread is not fully resolved and may or may not be a problem. Further analysis of these threads may be required.
Function Source
ntdll!ZwWaitForSingleObject+15
KERNELBASE!WaitForSingleObjectEx+98
kernel32!WaitForSingleObjectExImplementation+75
kernel32!WaitForSingleObject+12
xmltooling1_4!xmltooling::URLEncoder::isBad+730
xmltooling1_4!xmltooling::ReloadableXMLFile::reload_fn+16d
kernel32!BaseThreadInitThunk+e
ntdll!__RtlUserThreadStart+70
ntdll!_RtlUserThreadStart+1b
Back to Top
Thread 10 - System ID 10828
Entry point 0x00000000
Create time 10/3/2012 9:00:20 PM
Time spent in user mode 0 Days 00:00:00.00
Time spent in kernel mode 0 Days 00:00:00.00
This thread is not fully resolved and may or may not be a problem. Further analysis of these threads may be required.
Function Source
ntdll!ZwWaitForSingleObject+15
KERNELBASE!WaitForSingleObjectEx+98
kernel32!WaitForSingleObjectExImplementation+75
kernel32!WaitForSingleObject+12
xmltooling1_4!xmltooling::URLEncoder::isBad+730
xmltooling1_4!xmltooling::URLEncoder::isBad+5b0
xmltooling1_4!xmltooling::ReloadableXMLFile::reload_fn+161
kernel32!BaseThreadInitThunk+e
ntdll!__RtlUserThreadStart+70
ntdll!_RtlUserThreadStart+1b
Back to Top
Thread 11 - System ID 12068
Entry point 0x00000000
Create time 10/3/2012 9:00:20 PM
Time spent in user mode 0 Days 00:00:00.00
Time spent in kernel mode 0 Days 00:00:00.00
This thread is not fully resolved and may or may not be a problem. Further analysis of these threads may be required.
Function Source
ntdll!ZwWaitForSingleObject+15
KERNELBASE!WaitForSingleObjectEx+98
kernel32!WaitForSingleObjectExImplementation+75
kernel32!WaitForSingleObject+12
xmltooling1_4!xmltooling::URLEncoder::isBad+730
xmltooling1_4!xmltooling::URLEncoder::isBad+5b0
xmltooling1_4!xmltooling::ReloadableXMLFile::reload_fn+161
kernel32!BaseThreadInitThunk+e
ntdll!__RtlUserThreadStart+70
ntdll!_RtlUserThreadStart+1b
Back to Top
Thread 12 - System ID 19224
Entry point 0x00000000
Create time 10/3/2012 9:00:20 PM
Time spent in user mode 0 Days 00:00:00.00
Time spent in kernel mode 0 Days 00:00:00.00
This thread is not fully resolved and may or may not be a problem. Further analysis of these threads may be required.
Function Source
ntdll!ZwWaitForSingleObject+15
KERNELBASE!WaitForSingleObjectEx+98
kernel32!WaitForSingleObjectExImplementation+75
kernel32!WaitForSingleObject+12
xmltooling1_4!xmltooling::URLEncoder::isBad+730
xmltooling1_4!xmltooling::URLEncoder::isBad+5b0
xmltooling1_4!xmltooling::ReloadableXMLFile::reload_fn+161
kernel32!BaseThreadInitThunk+e
ntdll!__RtlUserThreadStart+70
ntdll!_RtlUserThreadStart+1b
Back to Top
Thread 13 - System ID 1048
Entry point 0x00000000
Create time 10/3/2012 9:00:45 PM
Time spent in user mode 0 Days 00:00:00.031
Time spent in kernel mode 0 Days 00:00:00.015
This thread is waiting on data to be returned from another server via WinSock.
The call to WinSock originated from shibsp1_4!shibsp::ListenerService::init+14df
Function Source
ntdll!ZwWaitForSingleObject+15
mswsock!SockWaitForSingleObject+3a
mswsock!WSPSelect+3a6
ws2_32!select+494
shibsp1_4!shibsp::ListenerService::init+14df
shibsp1_4!shibsp::ListenerService::init+115c
kernel32!BaseThreadInitThunk+e
ntdll!__RtlUserThreadStart+70
ntdll!_RtlUserThreadStart+1b
Back to Top
Thread 14 - System ID 16560
Entry point 0x00000000
Create time 10/3/2012 9:00:45 PM
Time spent in user mode 0 Days 00:00:00.015
Time spent in kernel mode 0 Days 00:00:00.00
This thread is not fully resolved and may or may not be a problem. Further analysis of these threads may be required.
Function Source
KERNELBASE!RaiseException+58
msvcr100!_CxxThrowException+48 f:\dd\vctools\crt_bld\self_x86\crt\prebuild\eh\throw.cpp @ 157
shibsp1_4!shibsp::Handler::preserveRelayState+3a3
shibsp1_4!shibsp::SAML2ArtifactResolution::emptyResponse+caba
shibsp1_4!shibsp::SAML2ArtifactResolution::emptyResponse+c40b
shibsp1_4!shibsp::ListenerService::receive+227
shibsp1_4!shibsp::ListenerService::init+189a
shibsp1_4!shibsp::ListenerService::init+14ef
shibsp1_4!shibsp::ListenerService::init+115c
kernel32!BaseThreadInitThunk+e
ntdll!__RtlUserThreadStart+70
ntdll!_RtlUserThreadStart+1b
Back to Top
Exception Information
In SHIBD_~2.DMP the assembly instruction at KERNELBASE!RaiseException+58 in C:\Windows\SysWOW64\KERNELBASE.dll from Microsoft Corporation has caused an unknown exception (0xe06d7363) on thread 14
Module Information
Image Name: C:\Windows\SysWOW64\KERNELBASE.dll Symbol Type: PDB
Base address: 0x00905a4d Time Stamp: Sat Jul 16 00:27:05 2011
Checksum: 0x00000000 Comments:
COM DLL: False Company Name: Microsoft Corporation
ISAPIExtension: False File Description: Windows NT BASE API Client DLL
ISAPIFilter: False File Version: 6.1.7601.17651 (win7sp1_gdr.110715-1504)
Managed DLL: False Internal Name: Kernelbase
VB DLL: False Legal Copyright: © Microsoft Corporation. All rights reserved.
Loaded Image Name: KERNELBASE.dll Legal Trademarks:
Mapped Image Name: Original filename: Kernelbase
Module name: KERNELBASE Private Build:
Single Threaded: False Product Name: Microsoft® Windows® Operating System
Module Size: 280.00 KBytes Product Version: 6.1.7601.17651
Symbol File Name: c:\symcache\wkernelbase.pdb\FDF353DA71FE45CD953EBEC8ED6D14AB1\wkernelbase.pdb Special Build: &
Script Summary
Script Name Status Error Code Error Source Error Description Source Line
CrashHangAnalysis.asp Completed
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the commits
mailing list