The thread '<No Name>' (0x9) has exited with code 0 (0x0)

I have a spider and a t43 display and i am getting these errors when i touch the display. in the immediate window i am getting
The thread ‘’ (0x9) has exited with code 0 (0x0).
The thread ‘’ (0xa) has exited with code 0 (0x0).
The thread ‘’ (0x3) has exited with code 0 (0x0).
The thread ‘’ (0xc) has exited with code 0 (0x0).
The thread ‘’ (0xb) has exited with code 0 (0x0).
The thread ‘’ (0xe) has exited with code 0 (0x0).
The thread ‘’ (0xd) has exited with code 0 (0x0).
The thread ‘’ (0xf) has exited with code 0 (0x0).
The thread ‘’ (0x10) has exited with code 0 (0x0).
The thread ‘’ (0x11) has exited with code 0 (0x0).
The thread ‘’ (0x12) has exited with code 0 (0x0).
The thread ‘’ (0x13) has exited with code 0 (0x0).

any ideas as to why?

i used other display with other mainboards and it never generated these messages before.
is this okay to ignore or will it eventually lock up the system and crash it?

Yes, when a thread exits with “code 0 (0x0)” it means that it has successfully executed and closed. This is nothing to worry about.

It sounds like there is something in the driver for the screen that’s opening a new thread on touch. Possibly to keep the display from locking up while it processes something. It might pay to check the source code for the driver and see.

EDIT: I had a quick look at the source code and can’t see any threading in the driver. Maybe a call to part of the netmf core is doing it. I did notice that ‘Microsoft.SPOT.Touch’ has a using statement for ‘System.Threading’ but I can’t actually see it being used anywhere.

You can “filter out” these diagnostics messages by unchecking the item in the context menu in the output window.

2 Likes