SynthMaker

SM2.02 many crashes

Archive · 2011 8 old posts

From the original SynthMaker forum (2004–2014), with its members’ names and dates.

infuzion ·

original topic: SM2.02 crash reporter locks up WinXP then BSOD When working on a large (25Mb) OSM, SM's crash reporter will lock up on random crashes. When I try to CTRL-ALT-DEL to stop SM, it will go directly to a BSOD. Files about to be sent. I have no idea why SM crashes, aside from the usual guess of just copy/pasting/leaving SM open too long.

Malc, please stop SM from crashing, & help it handle crash reports from large OSMs.

rl ·

BSOD looks suspiciously like a driver issue. ASIO or DirectSound?

trogluddite ·

I remember ages back having a big .osm that crashed a lot. It had a lot of mem's, code arrays etc. I found that it was gobbling up all my memory - every time the code was re-compiled (cut/pastes, that kind of thing), it just ate another big chunk of memory, presumably instead of just re-using the same bits - until there was no more memory..... then BSOD.

Haven't had it happen for a while - but I don't remember the specific bug ever being mentioned as fixed - maybe it's just that I haven't tinkered with the memory hungry bits of an .osm for a long time. I could see the effect quite clearly on the Task Manager memory readouts - so it might be worth having a look to see if you have a memory muncher on your hands.

BTW. This was also on a WinXP machine (1Gb RAM)

infuzion ·

Could be Drivers, though I lean more towards trogluddite's idea; SM's editor does seem to have memory issues always bugging it, though it does get better.

infuzion ·

Hmm, getting a crash every few hours of use... this time I only did about 5 minutes of cut & pasting, & editing a few lines in 2 ASM blocks, & SM crashed to desktop. At least it didn't crash to BSOD this time. I hope these crashes can be fixed soon; crash reporting is costing me money now.

sunsynth ·

My v2.02 crashed because of a bad ASIO kernel driver before...

now i have a RGY project only (Midi I/O w/o blue or poly stream) with over 520000 mods and i get strange dashed red Loop lines errors where i really don't expected them...

maybe this is because of the use of a special Midi Network driver -> dunno

trogluddite ·

My ASIO driver will also crash SM - always has for all the old versions too. But it's only when the .osm's are very SMALL, and I'm making an effect with a chain of blue streams between ASIO in and ASIO out. Even more odd - if I connect a mono readout to my ASIO in, then delete it again - I can then always connect up my in->out chain without a problem! Otherwise SM202 has been very stable for me so far.

infuzion ·

My last crashe were with DS Out, though I did suspect ASIO before.

Wrote something here? To have a post removed or your name hidden, write to [email protected].

Before your first post

A few rules keep this a friendly place. You agree to them once.

Shown next to what you post, here and in the app. It doesn’t have to be your real name: 3–24 lower-case letters, digits or _ (capitals become lower case, spaces become _).

    Then your post goes up straight away.

    Delete this reply?

    Open it in SynthMaker?

    It goes on the track you’re editing there, in place of that track’s sound, and into My sounds. Your other tracks stay as they are.

    Want to keep that track’s sound? Start a new song in SynthMaker first (Song › New song), then open this.

    Report this reply?

    Only the developer reads reports. The person isn’t told who reported them.

    What’s wrong with it?

    Block this person?

    You won’t see their posts and replies here any more. They aren’t told, and you can unblock them at any time.

    People you’ve blocked

    Their posts and replies are hidden from you. Unblock someone to see them again.

    The community rules

    A few rules keep this a friendly place. Everyone agrees to them once, before their first post.