http://bugs.winehq.org/show_bug.cgi?id=16258
--- Comment #2 from Anastasius Focht focht@gmx.net 2008-12-15 04:26:49 --- Hello,
I could not resist to dig further otherwise I can't get a good sleep ;-| It turns out this is in fact a bug in the original .NET 2.0 Framework (unpatched/no upgrade/no sp).
The same happens when the ngen worker is compiling the assemblies to native images in virgin XP + original .NET 2.0 Framework. Most likely a bug in handling unmanaged dependencies.
Dumping the list of memory mappings from the compiling process at a certain point showed indeed a large number of mappings of the same file "OgreNativeWrapper.dll" - all having different base addresses. Interestingly process utilities like "process explorer" or "handle/handlex" from the infamous sysinternals team (now M$) don't show the mappings as open file handles. Mysterious...
The standard limit of 1024 open file descriptors bites again... I'll add a workaround (ulimit) to appdb.
Maybe AJ comes up with clever idea but that would most likely require redesign (management of file mappings). I'd suggest to close this as WONTFIX.
Regards
addendum: It might be worthwhile to check .NET 2.0SP1 if it exhibits the same problem - when the SP1 installer is fixed ;-)