On Sun, 2003-10-19 at 14:52, J�rg Rosenkranz wrote: > > If the shared memory is corrupted, the runtime reverts to a non-shared > > setup. This has the side effect of preventing process forking. > > > We have this behaviour on one (and only one) of our machines. We were > not been able to track this issue down yet. Could this be a race > condition between two processes? We are starting multiple instances of > one Mono app from another multithreaded Mono app.
It's possible, but the code that creates the shared area tries to be very careful about races. There used to be a race between exiting one mono instance and starting a new one at the same time, but that manifested itself as a failed assertion. I'm assuming that all your machines have identical software installed, and that mono is up-to-date. Have you looked into potential hardware issues with the machine giving the problems? Make sure your memory isn't faulty, etc. - Dick _______________________________________________ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
