[Mono-list] Strange errors due to ~/.wapi problems
26 Aug 2003 14:27:37 +0100
On Mon, 2003-08-25 at 09:59, Dag Wieers wrote:
> I've got some strange behavior running a program on one of my machines. On
> another machine it is working properly. When I run the Tray Icon, it
> starts up normally (although it prints WARNING **: Shared memory sanity
> check failed.), but when I click on a menu-item that normally would invoke
> an external command I get:
If the shared memory is corrupted, the runtime reverts to a non-shared
setup. This has the side effect of preventing process forking.
You can delete the shared memory files in ~/.wapi when this happens, but
it would be very useful if you could track down _why_ the corruption
occurred. Running out of space might do it, but the sanity check looks
at the first few bytes.