I've been experiencing some crashes that don't generate a crash dump and don't get logged. I can see in the log that on the next start Waveform is aware that there was a crash and uploads the most recent dump file. That means you're getting the same file sent to you over and over and it has nothing to do with the recent crashes.
What should I do? I don't think either of us wants you flooded with irrelevant information. Delete the old dump files?
By the way, the problem seems to be associated with Klevgrand Tines and I think it's happening when that VST is being un-loaded. I've noticed it happening when I close an edit. But it's not something that I can reproduce with consistency.
Windows 10
Waveform Version 11.0.22 (Built: 10 March 2020) (64-bit)
Klevgrand Tines v1.0.3
Dump-less crashes
-
- KVRAF
- 1790 posts since 30 Dec, 2012
Can you send us your log file to support@tracktion.com?
From that we can take a look at the crash and find the anonymised but symbolicated crash on our servers.
From that we can take a look at the crash and find the anonymised but symbolicated crash on our servers.
-
- KVRer
- 26 posts since 26 Jan, 2019
I've been having the same problem with Waveform 10.
Lots of crashes, including ones that require a reboot as the audio engine is still running but not functioning.
I've assumed (perhaps wrongly) that my crashes were at least being logged and sent to Tracktion, but it doesn't appear to be so, looking at the crash files.
I find Ozone 8 standard particularly troublesome.
Also the Collective plugin sometimes freaks out with 100% CPU use, glitching the whole system. From here on, sound is choppy and clicky, and Waveform needs restarting.
Lots of crashes, including ones that require a reboot as the audio engine is still running but not functioning.
I've assumed (perhaps wrongly) that my crashes were at least being logged and sent to Tracktion, but it doesn't appear to be so, looking at the crash files.
I find Ozone 8 standard particularly troublesome.
Also the Collective plugin sometimes freaks out with 100% CPU use, glitching the whole system. From here on, sound is choppy and clicky, and Waveform needs restarting.
-
- KVRAF
- Topic Starter
- 4891 posts since 3 Jan, 2003 from Vancouver
I've send the log file, I think it was yesterday. You are undoubtedly getting many, many reports from me and they include crash dumps that have nothing to do with the problems I'm having. Please note that my request was primarily to find out how to avoid sending you junk and junk and junk and junk and junk and junk. You're getting lots of crash dumps that are old an irrelevant. If I can just find and delete the old crash dumps please let me know.dRowAudio wrote: Mon Mar 30, 2020 9:44 am Can you send us your log file to support@tracktion.com?
From that we can take a look at the crash and find the anonymised but symbolicated crash on our servers.
Surely there must be consensus by now...