Bug 684898 - Softdebugger for Windows shows Finalizer Thread
Summary: Softdebugger for Windows shows Finalizer Thread
Status: NEW
Alias: None
Product: Mono: Runtime
Classification: Mono
Component: debug (show other bugs)
Version: 2.10.x
Hardware: x86 Windows 7
: P5 - None : Normal
Target Milestone: ---
Assignee: Mono Bugs
QA Contact: Mono Bugs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-04 16:06 UTC by andreas flucke
Modified: 2011-04-05 07:14 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description andreas flucke 2011-04-04 16:06:48 UTC
User-Agent:       Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C; .NET4.0E)

The Finalizer Thread should be hidden.
There can appear unhandled exceptions which maybe can be normal (?)
in freeing resources in an undetermined way.

Reproducible: Always

Steps to Reproduce:
1.
2.
3.
Comment 1 Forgotten User vxPDddArjq 2011-04-04 18:12:16 UTC
The debugger UI can hide the finalizer thread if it wants to, the debugger backend won't hide it.
Comment 2 andreas flucke 2011-04-05 06:30:43 UTC
Maybe i'm wrong, but my observation is that this Thread doesn't show up in Linux. (The same App which causes unhandled Ex in this Thread)
Sorry for asking you here which way there is to hide the Thread in the UI except for getting it's Name (which is somewhat awkward)
Comment 3 Forgotten User vxPDddArjq 2011-04-05 07:14:25 UTC
This thread is created before the VM_START event is sent, so the app doesn't get a THREAD_START event for it. No idea why this works differently on windows, it shouldn't.