Steema Central

Hello,

After experiencing several freeze in our web application, we have used DebugDiag to try and identify a root cause. Apparently, a single thread is trying to display a message box - hardly useful for a server-side component -, thereby locking all other threads which are using the component.

The following threads in IIS_COM+__Date__06_04_2009__Time_11_55_44AM__w3wp.exe__DefaultAppPool__PID__6236__406__Manual Dump.dmp are displaying a message box. The call to display the message box originated from user32!NtUserWaitMessage+c.

Thread 149 - System ID 8180
Entry point msvcrt!_endthreadex+2f
Create time 04/06/2009 11:45:14
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 displaying a message box. The call to display the message box originated from user32!NtUserWaitMessage+c.

The text of the message being displayed is:



Function Source
ntdll!KiFastSystemCallRet
user32!NtUserWaitMessage+c
user32!InternalDialogBox+d0
user32!SoftModalMessageBox+94b
user32!MessageBoxWorker+2ba
user32!MessageBoxTimeoutW+7a
user32!MessageBoxTimeoutA+9c
user32!MessageBoxExA+1b
user32!MessageBoxA+45
TeeChart8+1ccfb
TeeChart8+1ca6c
ole32!CreateInprocInstanceHelper+1c
ole32!ICoCreateInstanceEx+cb
ole32!CComActivator::DoCreateInstance+6a
ole32!CoCreateInstanceEx+23
ole32!CoCreateInstance+3c
asp!ViperCreateInstance+18
asp!CComponentObject::TryInstantiate+78
asp!CComponentObject::Instantiate+26
asp!CPageComponentManager::AddScopedUnnamedInstantiated+5f
asp!CTypelibCache::CreateComponent+c6
asp!CServer::CreateObject+66
oleaut32!DispCallFunc+16a
oleaut32!CTypeInfo2::Invoke+234
asp!CDispatchImpl<IServer>::Invoke+55
vbscript!IDispatchInvoke2+b2
vbscript!IDispatchInvoke+59
vbscript!InvokeDispatch+13a
vbscript!InvokeByName+42
vbscript!CScriptRuntime::RunNoEH+22b2
vbscript!CScriptRuntime::Run+62
vbscript!CScriptEntryPoint::Call+51
vbscript!CSession::Execute+b4
vbscript!COleScript::ExecutePendingScripts+144
vbscript!COleScript::SetScriptState+14d
asp!CActiveScriptEngine::TryCall+19
asp!CActiveScriptEngine::Call+31
asp!CallScriptFunctionOfEngine+5b
asp!ExecuteRequest+17e
asp!Execute+24c
asp!CHitObj::ViperAsyncCallback+3f0
asp!CViperAsyncRequest::OnCall+92
comsvcs!CSTAActivityWork::STAActivityWorkHelper+32
ole32!EnterForCallback+c4
ole32!SwitchForCallback+1a3
ole32!PerformCallback+54
ole32!CObjectContext::InternalContextCallback+159
ole32!CObjectContext::DoCallback+1c
comsvcs!CSTAActivityWork::DoWork+12d
comsvcs!CSTAThread::DoWork+18
comsvcs!CSTAThread::ProcessQueueWork+37
comsvcs!CSTAThread::WorkerLoop+190
msvcrt!_endthreadex+a3
kernel32!BaseThreadStart+34


The text of the message being displayed is:


Has anyone ever seen this problem ? Is it a known bug ?

Hi LMA,

Please, could you send us a simple example project we can run "as-is" to reproduce the problem here?
You can either post your files at news://www.steema.net/steema.public.attachments newsgroup or at our upload page.

We can't reproduce the problem at will. It only happens after several days of continuous use.

Hi LMA,

When you'll find a consistent way we can to reproduce it here, we'll pleased to try to find a solution for you.

Hi,

Any chance you could use the callstack to determine the root cause of the problem ?
Or is there a way to get detailled debug symbols to produce a better stack next time it happens ?

Thank you.

Hi LMA,

I'm afraid that the only way we have to extract detailed information about the source of the problem would be having a simple application, running it during several days if needed in our server and debugging it when the crash succeeds.