[Mono-dev] Trying to reproduce _wapi_handle_unref bug - done and done

[Brian Crowell]

Brian Crowell wrote:
> I'm trying to reproduce a situation seen in my program involving the following 
> message:

After months of chasing this particular problem down, I think I finally found my 
problem. Here it is, with some I found on the way:


http://bugzilla.ximian.com/show_bug.cgi?id=79061 (killwapi.cs)

WAPI shared handles don't seem to disappear when the AppDomain does. This causes 
a really big problem, because a thread handle seems to appear for every 
AppDomain in existence. This program will exhaust the handle table.


http://bugzilla.ximian.com/show_bug.cgi?id=79062 (sigsegv.cs)

The combination of unquoted parameters and standard out redirects, over three 
attempts, will cause a SIGSEGV. Got this one entirely by accident.


http://bugzilla.ximian.com/show_bug.cgi?id=79063 (processdeadlock.cs)

This one is rare. There's a small chance of a deadlock if you run multiple 
processes simultaneously.

--Brian
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: processdeadlock.cs
Url: http://lists.ximian.com/pipermail/mono-devel-list/attachments/20060811/5bdbab3e/attachment.pl 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: sigsegv.cs
Url: http://lists.ximian.com/pipermail/mono-devel-list/attachments/20060811/5bdbab3e/attachment-0001.pl 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: killwapi.cs
Url: http://lists.ximian.com/pipermail/mono-devel-list/attachments/20060811/5bdbab3e/attachment-0002.pl