<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="edit-comment-hide">
<div class="markdown-body comment-body markdown-format js-comment-body"><p class="">I have a iOS project developed with XCode that uses libpd
to load a Pure Data patch. My project uses a mix of [osc~] and [phasor~]
with modulated parameters (pitch, volume, etc). My app is in 64-bit as
now required. I am using the latest version of Pure Data and libpd.</p><p class="">The Pure Data patch runs fine in Pure Data but it crashes in XCode. I
have an [osc~] that has its pitch modulated by an envelope. When I
change the value of the length of the envelope (= modulation rate) on a
device, it randomly crashes during testing but always on the same line
of libpd code. I thought it had to do with how fast the parameter was
changed but no, it also happens when the parameter is slowly changed.</p><p class="">Here is below a (reduced) patch where the problem occurs. I have
recently catched up with Pure Data. Any suggestions or corrections are
welcome.</p><p class="">modulatedOscillator.pd (<a href="http://forum.pdpatchrepo.info/uploads/files/upload-9c1506d8-30a2-4af3-8927-b4f97c73474e.pd" class="">http://forum.pdpatchrepo.info/uploads/files/upload-9c1506d8-30a2-4af3-8927-b4f97c73474e.pd</a>)</p><p class="">Here is a screenshot of the crash in XCode with the code sequence and the line of clock_unset that crashes.</p><p class=""><a href="https://cloud.githubusercontent.com/assets/10989820/7903859/79938d6a-07e9-11e5-97d6-28fb59664a6e.png" class="">https://cloud.githubusercontent.com/assets/10989820/7903859/79938d6a-07e9-11e5-97d6-28fb59664a6e.png</a></p><p class="">I have done some printing and it crashes in this function:</p><p class="">void clock_unset(t_clock *x){<br class="">
if (x->c_settime >= 0){<br class="">
if (x == clock_setlist) clock_setlist = x->c_next;<br class="">
else{<br class="">
t_clock *x2 = clock_setlist;<br class="">
while (x2->c_next != x) x2 = x2->c_next;<br class="">
x2->c_next = x->c_next;<br class="">
}<br class="">
x->c_settime = -1;<br class="">
}<br class="">
}</p><p class="">On this line :</p><p class="">while (x2->c_next != x) x2 = x2->c_next;</p><p class="">With a printed value of : x2->c_next==NULL</p><p class="">Someone replied to me about the issue on Stack Overflow:<br class="">
"it seems that the clock that is being unset is not found in the list of
currently maintained clocks. however, this is probably one of the most
often used functions in Pd and afaict you only use bog standard built-in
objects, which should make the patch pretty failsafe. i'm guessing that
your problem is related to the new multi-instance features of Pd and
you simply hit a bug."</p><p class="">Could it be a bug? Thanks in advance.</p>
</div></div></body></html>