A crash log would be nice to have. ~/Library/Logs/CrashReporter<br><br>
Running out of RAM should not cause a crash but rather a slowdown.<br>
<br><div><span class="gmail_quote">On 9/13/06, <b class="gmail_sendername">user @ earweego</b> <<a href="mailto:pd@earweego.net">pd@earweego.net</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
hello list,<br><br>for an installation in ZKM, we are using a GEM-based patch<br>where a dozen of cubes are textured via [pix_image] with jpg-images of 35kB on avg.<br>each cube changes its image about once per second,<br>
and we are getting heavy crashes after less than an hour.<br><br>using a MAC Dual G5 with OS X 10.4.4, 1.25GB RAM<br>and PD version pd++_0_39_1 by James Tittle<br>which is amazing for the rest - even fixed the tedious titlebar issue :)
<br><br>apparently,
the image buffer is not cleared after the new image was loaded, and
thus the RAM is overflowing. We could work around this problem by
changing the images less often, but it feels dirty as it would just
_delay_ the crash to a time beyond exhibition duration.<br>Would it help if the images had smaller pixel sizes and thus take less memory?<br>I guess the bug is known, but is anybody able to fix it before the opening in one week ?
<br><br>any hint would be greatly appreciated,<br>bests,<br> .hh.<br><br><br><br>_______________________________________________<br><a href="mailto:PD-list@iem.at">PD-list@iem.at</a> mailing list<br>UNSUBSCRIBE and account-management ->
<a href="http://lists.puredata.info/listinfo/pd-list">http://lists.puredata.info/listinfo/pd-list</a><br></blockquote></div><br>