Re: [Boost-bugs] [Boost C++ Libraries] #8683: windows native shared memory freeze when no more ram available

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #8683: windows native shared memory freeze when no more ram available
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2013-08-20 17:46:33

#8683: windows native shared memory freeze when no more ram available
-------------------------------+--------------------------
  Reporter:  julien.potiron@…  |      Owner:  igaztanaga
      Type:  Bugs              |     Status:  new
 Milestone:  To Be Determined  |  Component:  interprocess
   Version:  Boost 1.53.0      |   Severity:  Problem
Resolution:                    |   Keywords:
-------------------------------+--------------------------

Comment (by anonymous):

 There is no way to detect your problem. When you use windows_shared_memory
 (and CreateFileMapping win32 API), you are reserving memory that is backed
 by RAM plus the pagefile. When you start writing to the shared memory
 region, that memory must be in RAM so other programs and data must go to
 the pagefile to free RAM for your write. I don't know of any notification
 mechanism in windows to detect this behavior.

 You can try to map a portion of the file, write it and unmap it. Then you
 map a different portion. That could help windows to manage better the
 pagefile (as it only needs to care about the mapped region and not the
 whole shared memory object).

-- 
Ticket URL: <https://svn.boost.org/trac/boost/ticket/8683#comment:3>
Boost C++ Libraries <http://www.boost.org/>
Boost provides free peer-reviewed portable C++ source libraries.