App threads on XP cannot be killed because calling USB driver.

NTDEV
1

I have a USB driver, a device and Flash app. The Flash app has 2 worker
threads that communicate to driver. The Flash and USB driver work great
on 2000, ME, and 98. Somehow on XP, the 2 worker threads decided not to
die (Spy++ showed they are alive) even though the thread loop ends and the
output of Visual Studio shows that the two threads have exited. If I
comment out the driver accessing part, the the two threads work ok.

Any suggestion is appreciated.

Regards,
-De

2

What kind of operations do you do in the driver ? Things to look for are
a. References to process or that thread.
b. Thread blocked by waiting for objects in kernel mode (pass kernelMode to
the mode parameter to KeWaitForSingleObject).

–
Nar Ganapathy
Windows Core OS group
This posting is provided “AS IS” with no warranties, and confers no rights.
wrote in message news:xxxxx@ntdev…
>
> I have a USB driver, a device and Flash app. The Flash app has 2 worker
> threads that communicate to driver. The Flash and USB driver work great
> on 2000, ME, and 98. Somehow on XP, the 2 worker threads decided not to
> die (Spy++ showed they are alive) even though the thread loop ends and the
> output of Visual Studio shows that the two threads have exited. If I
> comment out the driver accessing part, the the two threads work ok.
>
> Any suggestion is appreciated.
>
> Regards,
> -De
>
>