Thanks for the crash.dmp file. It seems this particular crash occurred when quitting Podium, so I wonder if this is a different type of crash than the one you describe. Does the crash happen as soon as you record arm the track? If either of you have more crash.dmp files from other crashes I would appreciate if you can send them to me.
I’m sending another crash dump file for this issue. Here’s what I think I did.
Opened the project file
Added a child track to an existing group
Assigned an input
Record-armed the track
And the crash occurred. Podium just closed. I did not deliberately quit Podium.
This should clarify the email – shoulda’ checked before clicking send. It’s gotta be something specific to my project, as I can’t recreate this with a simple stub project with nothing recorded and no VST’s assigned.
Hopefully the fresh file can shed some light on what’s going on. Lemme know what else you need.
Podium 3.4.4 is now released, which should have these bugs fixed. Sorry for taking so long with the release. The crashes were due to null-pointer references, which is the most frequently occurring type of bug I’ve had to deal with over the years. In an effort to avoid these kinds of crash bugs in the future I have adopted a new system of how pointers/references are handled across the entire Podium codebase. If you encounter further crashes please do email the crash dump file to me.