search for: memory_management

...href="#trunkwxruby2swigtypemapi">trunk/wxruby2/swig/typemap.i</a></li> <li><a href="#trunkwxruby2swigwxi">trunk/wxruby2/swig/wx.i</a></li> </ul> <h3>Added Paths</h3> <ul> <li><a href="#trunkwxruby2swigmemory_managementi">trunk/wxruby2/swig/memory_management.i</a></li> </ul> </div> <div id="patch"> <h3>Diff</h3> <a id="trunkwxruby2swigcommoni"></a> <div class="modfile"><h4>Modified: trunk/wxruby2/swig/common.i...

...5-22 17:40:09 -0400 (Tue, 22 May 2007)</dd> </dl> <h3>Log Message</h3> <pre>Preserve Sizers associated with Windows from GC; fix several sample crashes on resizing.</pre> <h3>Modified Paths</h3> <ul> <li><a href="#trunkwxruby2swigmemory_managementi">trunk/wxruby2/swig/memory_management.i</a></li> <li><a href="#trunkwxruby2swigwxi">trunk/wxruby2/swig/wx.i</a></li> </ul> </div> <div id="patch"> <h3>Diff</h3> <a id="trunkwxruby2swigmemory_mana...

...lt;ul> <li><a href="#trunkwxruby2swigclassesAppi">trunk/wxruby2/swig/classes/App.i</a></li> <li><a href="#trunkwxruby2swigclassesMenuBari">trunk/wxruby2/swig/classes/MenuBar.i</a></li> <li><a href="#trunkwxruby2swigmemory_managementi">trunk/wxruby2/swig/memory_management.i</a></li> <li><a href="#trunkwxruby2swigwxi">trunk/wxruby2/swig/wx.i</a></li> </ul> </div> <div id="patch"> <h3>Diff</h3> <a id="trunkwxruby2swigclassesAppi...

I''ve spent a couple hours tracking through the code and reading Swig documentation to try to find out about tracking C objects back to Ruby objects. It''s not so easy to do. I took at look at wxPython and their source is a mess! I wasn''t able to glean anything from them on how they do it. My current hypothesis is to trap SWIG_NewPointerObj calls and build a map.

...n encoding from the command-line (flac.exe -8), as in me selecting a WAVE file for encoding from the command line. The errors always show as a Blue Screen Of Death (how I've come to hate my favorite color :\). I've seen several errors by now and I've written some down: PFN_LIST_CORRUPT, MEMORY_MANAGEMENT, UNEXPECTED_KERNEL_MODE_TRAP, etc. All involve the memory. So the obvious conclusion is that my memory is fried. However, I've played numerous games, used tons off programs, and none has ever triggered a BSOD. I'd say (from my limited insight in this) that CPU and memory intensive tasks lik...

...y2swigclassesStaticBoxSizeri">trunk/wxruby2/swig/classes/StaticBoxSizer.i</a></li> <li><a href="#trunkwxruby2swigclassesStdDialogButtonSizeri">trunk/wxruby2/swig/classes/StdDialogButtonSizer.i</a></li> <li><a href="#trunkwxruby2swigmemory_managementi">trunk/wxruby2/swig/memory_management.i</a></li> <li><a href="#trunkwxruby2swigsharedsizersi">trunk/wxruby2/swig/shared/sizers.i</a></li> <li><a href="#trunkwxruby2swigwxi">trunk/wxruby2/swig/wx.i</a></li> <...

...he reason Sean and I are not getting crashes is that Ruby GC is not collecting destroyed objects until shutdown - ie being overly conservative. So I re-read some docs to see what might be giving us problems: http://www.swig.org/Doc1.3/Ruby.html#Ruby_nn57 http://wxruby.rubyforge.org/wiki/wiki.pl?Memory_Management While the wiki page is useful, it''s important to bear in mind that it predates the release of SWIG 1.3.26, which includes the additional features for marking and tracking. So my first question is: 1) What''s the status of the handcoded memory management (especially in wx.i and...

Hi Kostya & Yury, Thanks for the advice. On 9 February 2016 at 22:48, Kostya Serebryany <kcc at google.com> wrote: > Hi Dan, > > On Tue, Feb 9, 2016 at 10:57 AM, Dan Liew <dan at su-root.co.uk> wrote: >> >> Hi, >> >> # TL;DR >> >> I've been building an application with and without the address >> sanitizer (with gcc 5.3 and

Hi, # TL;DR I've been building an application with and without the address sanitizer (with gcc 5.3 and clang 3.7.1) and I've observed that the application's behaviour changes (assertion hit/ not hit). I'm wondering if this could be a bug in address sanitizer or if the application I'm running is just buggy (e.g. doing bad things like relying on memory layout, etc.). I'm

Hello everyone, Excuse the title. I'm trying to do something very specific that goes against some common assumptions. I am aware of how Linux uses available memory to cache. This, in almost all cases, is desirable. I've spent years explaining to users how to properly read the free output. I'm now trying to increase VM density on host systems (by host, I mean the physical system, not