[Mono-bugs] [Bug 324318] Handling of out of memory issues

bugzilla_noreply at novell.com bugzilla_noreply at novell.com
Tue Sep 25 18:55:04 EDT 2007


Robert Jordan <robertj at gmx.net> changed:

           What    |Removed                                         |Added
                 CC|                                                |robertj at gmx.net

--- Comment #3 from Robert Jordan <robertj at gmx.net>  2007-09-25 16:55:03 MST ---
For the unmanaged world we could set up our own GLib allocation
functions with g_mem_set_vtable (), while preallocating some
buffers in advance, such that g_malloc () will not fail right
after the first out of memory condition.
Instead of failing, a "low watter" warning flag in GC could be set that
will cause the next managed allocation to fail.

The problem is the lack of determinism of this approach. It is
probably easily exploitable from managed code.

Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

More information about the mono-bugs mailing list