Thanks so much again!

I tried, and it didn't give me a good clue, though.
What I got as output is:
All zones: 1466 nodes malloced - Sizes: 117040KB[25] 96KB[25] 8KB[2] 5.5KB[1] 
5KB[1] 4KB[2] 3KB[3] 2.5KB[2] 2KB[4] 1.5KB[4] 656[15] 592[2] 528[2] 512[2] 
448[5] 400[3] 384[2] 368[3] 352[1] 336[1] 304[35] 288[19] 272[16] 256[29] 
240[8] 224[6] 208[40] 192[9] 176[15] 160[7] 144[5] 128[7] 112[30] 96[7] 80[32] 
64[115] 48[298] 32[553] 16[130]

So that does not account for the 5+GB (after a few minutes, and growing), I 
think.

Best regards, Gabriel




> On 30. Apr 2023, at 20:41, Rob Petrovec <petr...@mac.com> wrote:
>
> Oh yeah, Gabriel, another technique you can use is to start your app and 
> create a memgraph _before_ reproducing the problem.  Then reproduce the 
> problem and run ‘heap MyApp --diffFrom MyApp.memgraph’.  It will show the new 
> objects that have been created since the memgraph was taken, sorted number of 
> objects. That might narrow down what object(s) are eating your memory.  Good 
> luck.
>
> —Rob
>

Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Reply via email to