[GEM-dev] [ pd-gem-Bugs-3494265 ] pix_buffer crashes with high frame count

[SourceForge.net]

Bugs item #3494265, was opened at 2012-02-25 11:36
Message generated for change (Comment added) made by zmoelnig
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=507079&aid=3494265&group_id=64325

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Pixes (pix_ objects)
Group: osx
Status: Open
>Resolution: Postponed
Priority: 5
Private: No
Submitted By: max (maxn)
Assigned to: Nobody/Anonymous (nobody)
Summary: pix_buffer crashes with high frame count

Initial Comment:
the pix_buffer object crashes Pd completely if instantiated with a rediculous high size (number of frames) instead of gracefully showing an error message. This is tested with OS X and GEM: ver: 0.93.3 GEM: compiled: Nov 10 2011

----------------------------------------------------------------------

>Comment By: IOhannes m zmölnig (zmoelnig)
Date: 2012-02-26 07:20

Message:
this is by design...

Pd/Gem tries to allocate the frames you told it to do without checking
whether the numbers make sense or not (that's the "by design" part)
iirc, it also tries to catch any problems related to out.-of-memory, in
order to prevent a crash.

nevertheless, in practice it seems that no out-of-memory exeception is ever
thrown, and thus no counter measurements can take effect. instead the OS
decides to close the application (eventually after first eating up all the
swap space which might take literal ages)

nevertheless, if you can provide a back-trace and/or a solution to the
problem, i'll happily add a fix

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=507079&aid=3494265&group_id=64325