Well, the screenshot you posted of the allocation profiler shows e.g.:
25% of over 500mb worth of allocation is in sets. However, note that as
per your previous comments, you set an upper memory bound of 1.5gb and
you got the "No Space Left" dialog at about 1gb of used memory... if I
understand that correctly, then it's a symptom of something other than
excess allocations.
Note also that excess allocations per se are ok... it just makes the
application go slower because eventually it has to GC the garbage. But
if they do not go away, then it could be indicative of a memory leak or
some such...
On 1/24/2012 2:38 PM, Steve Cline wrote:
> As I mentioned ealier, I accept that the No Space error happens because I am
> making too much stuff. What I want is something that would tell me, for
> example, that between the start and stop of monitoring I created (X
> instances of class A, with a size of N), and (Y instances of class B, with a
> size of M), and so on.
>
> I am not as interested in 'this is the creation method that failed because
> it is the one that pushed me over some arbitrary boundary', but rather 'here
> is the breakdown of the stuff that gets created when you execute this code'.
> I suspect, but would like to prove, that my problem could be addressed by
> avoiding recreating the same objects (caching is an obvious solution, but
> there may be others - but I really want to know what objects get created)
>
> --
> View this message in context:
http://forum.world.st/Detect-cause-of-No-Space-Left-tp4271258p4325588.html> Sent from the VisualWorks mailing list archive at Nabble.com.
> _______________________________________________
> vwnc mailing list
>
[hidden email]
>
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc>
_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
Locked
