Posted by Joshua Ruppert on 08/08/06 20:27

Chung Leong wrote:
> Joshua Ruppert wrote:
> > It seems like I might be back to having a monitoring process to look
> > for orphaned processes. One detail I may not have included in our
> > discussion so far is that the orphanded processes are always lower in
> > memory usage (~100K - ~6,000K) than properly working processes
> > (~10,000K - ~14,000K). This tells me that it's probably failing before
> > it even gets to the db connection. Does that make sense?
>
> I wouldn't read too much into it. Memory management in Windows is quite
> complex. I believe the memory usage reported in task manager is the
> physical amount. A process that has stalled will have a smaller foot
> print since the OS would divert memory previously allocated to it to
> other processes.
>
> You can figure out where the process is stalling through Process
> Explorer. Go to properties then threads, select the php.exe thread and
> press the stack button. The item at the bottom is the last function
> called across a DLL. Somewhere in the chain you might see a function
> name SQLxxxxxx. That'd be a function in the ODBC driver.

Ok, It took a little while but I currently have one orphaned process
and it has just one thread and it seems to still be in the
initialization phase of the base PHP environment. The thread is labeled
as php.exe!OS_SetFlags+0xa0. The stack for the thread looks like this:
ntkrnlpa.exe+0x8cf3e
ntkrnlpa.exe+0x2927a
ntkrnlpa.exe+0x32cee
ntkrnlpa.exe+0x32f95
ntkrnlpa.exe+0x2927a
ntkrnlpa.exe+0x137e4c
ntkrnlpa.exe+0x88c6c
ntdll.dll!KiFastSystemCallRet
kernel32.dll!WaitForSingleObject+0x12
php4ts.dll!zend_timeout+0xac
php.exe+0x1e90
php.exe!OS_SetFlags+0x183
kernel32.dll!IsProcessorFeaturePresent+0x9e

Any thoughts?

[Back to original message]