I always run mono without --debug key, and memory is still leaking. I'll collect heapshot info of the my latest build and will post info from it in a day or two.
There is much worse thing. After long working mono crashes with a dump. Once or twice it told, that could not create thread (it's predictable that in my app could be a sutiation, when max threads limit is reached, but why mono drops in core and did not call AppDomain.CurrentDomain.UnhandledException?) Sometimes it tells about segmentation fault (maybe this is related to high fragmentation in GC). Sometimes mono drops into core without any human readable cause. Several times I saw "timeout reached in the finalizer thread". I have got some important data in the memory, which I want to save on the crash of mono. Maybe mono has a some extension, which I can use to register 'on crash' callback and save important data? -- View this message in context: http://mono.1490590.n4.nabble.com/Async-sockets-and-memory-leaks-in-BeginSend-tp4648844p4649559.html Sent from the Mono - General mailing list archive at Nabble.com. _______________________________________________ Mono-list maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-list
