incubator-stdcxx-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Farid Zaripov <Farid_Zari...@epam.com>
Subject RE: STD_BAD_ALLOC.cpp test problem on Windows
Date Mon, 18 Jun 2007 14:25:24 GMT
 > -----Original Message-----
 > From: Martin Sebor [mailto:sebor@roguewave.com]
 > Sent: Thursday, June 07, 2007 6:32 PM
 > To: stdcxx-dev@incubator.apache.org
 > Subject: Re: STD_BAD_ALLOC.cpp test problem on Windows
 >
 > Farid Zaripov wrote:
 > >> -----Original Message-----
 > >> From: Martin Sebor [mailto:sebor@roguewave.com]
 > >> Sent: Wednesday, June 06, 2007 9:45 PM
 > >> To: stdcxx-dev@incubator.apache.org
 > >> Subject: Re: STD_BAD_ALLOC.cpp test problem on Windows
 > >>
 > >> Still, are you aware of any Windows API that lets programs
 > limit the
 > >> amount of dynamic memory available to them, like
 > >> setrusage() does on UNIX? I ask because allocating so much storage
 > >> can put a big stress on the system, even if for just a few seconds.
 > >
 > >   The process memory (and/or user-mode time) can be limited
 > using job
 > > object, but this possibility available on Windows 2000 and
 > later (not
 > > available on Windows NT).
 >
 > That's better than nothing. Would it be pretty easy to do in the test?

  The proposed patch is attached.

Farid.


Mime
View raw message