D Language 2.0
Andrei Alexandrescu
SeeWebsiteForEmail at erdani.org
Thu Jan 21 16:17:53 PST 2010
Bill Baxter wrote:
> On Thu, Jan 21, 2010 at 2:43 PM, Andrei Alexandrescu
> <SeeWebsiteForEmail at erdani.org> wrote:
>> Walter Bright wrote:
>>> retard wrote:
>>>> On Linux the processes almost always stay on main memory, and only start
>>>> to fill swap when running out of main memory. So unless you have no swap set
>>>> up, OOM cannot happen unless the swap is >95% filled. OOM inside the GC's
>>>> virtual memory space can happen earlier, of course.
>>> Yeah, that's another thing I should have mentioned. When you're running
>>> Windows or Linux at the edge of running out of virtual memory, which is when
>>> the gc would fail to allocate memory, the system tends to go unstable
>>> anyway.
>>>
>>> This is because (as I mentioned before) few apps handle out of memory
>>> properly.
>> Please stop spreading that information. Even if it has truth to it, it's not
>> a reason to throw our hands in the air. In my field apps routinely encounter
>> and handle the problem of running tight on memory.
>>
>> Let me make it very clear: I have had malloc return 0 on me.
>
> .... and recovered? Or didn't?
Sure as heck recovered. I couldn't afford to lose all of the good work
I'd done in the previous 7 hours.
Andrei
More information about the Digitalmars-d
mailing list