help-smalltalk
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Help-smalltalk] Strategy to finding memleaks


From: Holger Hans Peter Freyther
Subject: Re: [Help-smalltalk] Strategy to finding memleaks
Date: Sat, 09 Apr 2011 22:41:57 +0200
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.15) Gecko/20110307 Fedora/3.1.9-0.39.b3pre.fc14 Lightning/1.0b2 Thunderbird/3.1.9

On 04/09/2011 09:29 PM, Holger Hans Peter Freyther wrote:
>

Hi Paolo,

this seems a bit weird. once we add allocPtr + BYTES_TO.. and then we just do
allocPtr + size. I am not sure about the difference but it looks wrong. This
also raises the question when/if the eden is shrinked? I will try to find the
answer for that now.

@@ -762,13 +762,16 @@ _gst_alloc_obj (size_t size,
      GC, so we use a local var to hold its new value */
   newAllocPtr = _gst_mem.eden.allocPtr + BYTES_TO_SIZE (size);

  if UNCOMMON (size >= _gst_mem.big_object_threshold)


   if UNCOMMON (newAllocPtr >= _gst_mem.eden.maxPtr)
     {
       _gst_scavenge ();
-      newAllocPtr = _gst_mem.eden.allocPtr + size;
+      newAllocPtr = _gst_mem.eden.allocPtr + BYTES_TO_SIZE(size);
     }




reply via email to

[Prev in Thread] Current Thread [Next in Thread]