1.1.6: Editor still crashing

mwvdlee · 4 Feb 2010

I don't quite know the conditions, but 1.1.6 seems to be crashing a lot more than 1.1.5. 1.1.5 would be stable all day unless I did some stupid things with infinite loops or faulty ASM, but 1.1.6 seems to crash on completely unexpected and arbitrary times on schematics that worked just fine (unchanged!) in 1.1.5

malc · 4 Feb 2010

@mwvdlee:

Are you sure that you're doing exactly the same thing that you were doing in 1.1.5? It would be handy if you could try and find a way of replicating any issues. The beta testing for 1.1.6 was very extensive and nobody reported any general decrease in stability. Perhaps it's a problem that's specific to whatever you're working with? It would be great if you could narrow it down.

@infuzion:

Thanks for the files. How do I replicate this? I tried playing around but didn't get a crash. Are you able to duplicate it?

Thanks.

Mo · 4 Feb 2010

I have some crashes/freeze here too. Both in editor and VST's. I found it related to a readout from a knob. Deleting/disconnect from MGUI the readout and it seems stable.

Try add a mono readout to a Example Synth animated knobs green out instead of label. Already there i have a SM crash but i could not replicate it. Then export as VST and open in FL. There i have freeze on automation and on save sometimes. Sometimes FL freeze after some time of automation of the knob with readout. Seems unstable and sometimes it works. So a bit difficult to replicate directly.

So SM 1.1.6 seems more unstable with this but also SM 1.1.5 freeze VST after automate some time a knob with a readout. I will investigate further as it's the only problem left before my synth is ready. The readout freezes the VST after few minutes automation. I tried limit redraws but it seems to be related to string change or something there (also in SM 1.1.5 and before).

Mo · 4 Feb 2010

I can replicate it now. Here is only a LFO from analog kit with a preset manager automated in FL. Just press start and let it run in FL. First it looks fine but after some time not stopping it, maybe 30 mins, it freeze and FL stop working.

infuzion · 4 Feb 2010

malc wrote: @infuzion: Thanks for the files. How do I replicate this? I tried playing around but didn't get a crash. Are you able to duplicate it?

I detailed exactly what I did in the email; simply renamed the 2 module, copy/paste, connected them, played 2 notes, switched from the 1st to 2nd OSC, played a note, triggered the button on the 2nd OSC, then it crashed then or after I triggered another note.

I do not have time to do any more testing; I simply have to move on to something else more stable & that can generate me some money. If Outsim wants to hire me on a contractual/hourly basis, then I can help you out. I'll wait for another version to use SM. Thanks for your concern & efforts.

MegaHurtz · 4 Feb 2010

I have to add, it is`nt at it`s best behavour here, have to postpone it for a day maybe but im shure I can make a "rock solid version" of the box plot.. So probbably due to me also. (it`s the recompile thing), I have a solution.

malc · 5 Feb 2010

@infuzion:

I did try those steps but it didn't fall over so I was just wondering if it crashes consistently with you when you execute these steps. Anyway no problem, I completely understand you have to make the best use of your time, thanks for all your help. It would be great if we were in a position to hire testers but unfortunately that's not possible :-( We do very much appreciate all the help we get though.

@Mo:

Thanks for this, I can duplicate the freeze too. Seems to be linked to the Format String component that's being used to display the frequency. I need to dig deeper but I'm testing now having deleted that component and so far no crash after quite some time of running (it certainly fell much earlier than this in previous tests where the component was still present).

Mo · 5 Feb 2010

malc wrote: @Mo:

Thanks for this, I can duplicate the freeze too. Seems to be linked to the Format String component that's being used to display the frequency. I need to dig deeper but I'm testing now having deleted that component and so far no crash after quite some time of running (it certainly fell much earlier than this in previous tests where the component was still present).

Yep but knobs without a readout to GUI but Format String connected to VST Parameters Display value only, seems works fine. Also the more redraws the faster freeze. Like something is not released properly and get filled up.

malc · 5 Feb 2010

Indeed, it needs both to be there - so a Format String and a readout to display the result. It appears to be a threading issue. The readout is being redrawn on the GUI thread and the value comes from the automation thread. Both access the same string resource and that's where the problem lies.

I've added some access protection now and it's been running for the last half hour or more with no freeze. I reckon that's nailed it.

Thanks for your help!

MichaelBenjamin · 5 Feb 2010

the format string primitive also caused crashes of compiled vsts in earlier versions quite quickly when stressed. could not find the thread atm.

malc · 5 Feb 2010

I'd say most likely the same thing then, so it'll be good to have this resolved 🙂

Mo · 12 Feb 2010

So malc is this fixed? Need this fixed before i can release anything or it will be pretty unstable with automation and my knobs. Ready to test a new beta.. 🙂