- **labels**: --> crash, gemlist, separator - **status**: open --> pending-works-for-me - **assigned_to**: IOhannes m zmölnig - **OS**: --> any - **Release**: --> 0.94 - **Comment**:
seems like i cannot reproduce these bugs any more (at least on linux).
can you confirm that this somehow got fixed?
---
** [bugs:#193] gemlist and separator may crash**
**Status:** pending-works-for-me **OS:** any **Release:** 0.94 **Labels:** crash gemlist separator **Created:** Fri May 04, 2012 01:05 PM UTC by Cyrille Henry **Last Updated:** Fri May 04, 2012 01:05 PM UTC **Owner:** IOhannes m zmölnig
gemlist and separator did not work well together. here are 2 example that can lead to a pd crash. - gemlist flow by a separator and a pix_image is manually banged - gemlist follow by a separator is not update by a valid gemlist at every frame
both are "incorrect" use of gemlist, but it should not crash. so, i suggest to limit bang action on gemlist only if both condition occur : - bang happend during gem rendering - a valid gemlist is received on it's right inlet at this frame
i don't think of any restriction imposes by this limitation, but I may be wrong.
attachement are 2 crasher patch
---
Sent from sourceforge.net because gem-dev@lists.iem.at is subscribed to https://sourceforge.net/p/pd-gem/bugs/
To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/pd-gem/admin/bugs/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
-
"IOhannes m zmölnig"