CWebBrowser thread debug results.(Windows 95 vs Windows NT)

=?ISO-8859-1?Q?Guillermo_G=F3mez_Valc=E1rcel?= -- guille@baratz.es
Friday, January 24, 1997

Environment: VC++4.2b, Win95, Windows NT 4.0

	I had integrated in my application the Web Browser control and I have on=
ly
used the Navigate() function. I had seen that during the creation it runs
one thread more and during the navigate it runs six threads more. Four of
the last six threads auto exit correctly (with code 0) when the control h=
as
no activity; but the rest is still executing although the Web Browser
control is destroyed.

	When the application is finished, it also exit the execution of your
pending threads, but this exit on Windows 95 with code -1, while on Windo=
ws
NT exit with code 0.

	This is the results of my window debug on Windows 95:

Loaded symbols for 'C:\WINDOWS\SYSTEM\MFCO42D.DLL'
Loaded symbols for 'C:\WINDOWS\SYSTEM\MSVCRTD.DLL'
Loaded symbols for 'C:\WINDOWS\SYSTEM\MFC42D.DLL'
The thread 0xFFF0216F has exited with code 0 (0x0).
The thread 0xFFF02353 has exited with code 0 (0x0).
The thread 0xFFF3E007 has exited with code 0 (0x0).
The thread 0xFFF04AF3 has exited with code 0 (0x0).
The thread 0xFFFD77C3 has exited with code -1 (0xFFFFFFFF).
The thread 0xFFF3C2CF has exited with code -1 (0xFFFFFFFF).
The thread 0xFFF28707 has exited with code -1 (0xFFFFFFFF).
The program 'C:\Absys5\WinDebug\Absys5.exe' has exited with code 0 (0x0).

Why the thread execution is not finished when the control is destroyed?
Why these threads exit with code -1 on Windows 95?

Thanks, Guillermo

Guillermo G=F3mez Valc=E1rcel

Baratz, Servicios de Teledocumentaci=F3n S.A.
<http://www.baratz.es>

---

Mike Blaszczak -- mikeblas@nwlink.com
Sunday, January 26, 1997

At 11:22 1/24/97 +0100, Guillermo G=F3mez Valc=E1rcel wrote:
>Environment: VC++4.2b, Win95, Windows NT 4.0

>I had integrated in my application the Web Browser control and I have only
>used the Navigate() function. I had seen that during the creation it runs
>one thread more and during the navigate it runs six threads more. Four of
>the last six threads auto exit correctly (with code 0)

The exit code of a thread has nothing to do with it "correctly" terminating.
The exit code can be whatever the designer wants it to be.  It is a very
simple mechanism for communicating information back to the owner.

>Why the thread execution is not finished when the control is destroyed?
>Why these threads exit with code -1 on Windows 95?

Because that's the way the control was designed. The messages and
behaviour you note are benign.=20


.B ekiM
http://www.nwlink.com/~mikeblas/
Why does the "new" Corvette look like a 1993 RX-7?
These words are my own. I do not speak on behalf of Microsoft.

---

| Вернуться в корень Архива |