Crash on quit. I wish I could attach the log

I have a WL12 generated crash, but can’t upload the RAR zip here due to a 4mb limit. Mine is just under 11mb. The .dmp is a bit over 5mb.

Where and how should I submit this crash report?

The crash is consistent as long as I load a wave file into the editor. Simply opening WL12 and closing it does not produce the crash.

1 Like

@PG1 is the above an AI or bot problem? I don’t see that as a solution when the crash report is already a RAR file.

Wavelab keeps crashing In previous posts all these are on file storage shared.

When any file is .RAR you can use WINRAR and extract everything to a folder. You can then Archive that folder as 4 different files (as shown in the picture above) of 3.5 MB each and attach everything to one thread on this forum.

When the crash happens, there is a email send option. Use that.

Correct.

After a crash has been detected I press Submit Bug.

Is the correct address ?

That address does not seem to work. “error can’t send error request to the server” then I have to press OK.

I suppose I could use my own email address and attach the crash log, and send it to gotowave@gmail, but I became suspicious of the gotowave address.

Would that be ok to send it from my personal email?

The email is correct

Thanks PG Ill send it via my own email. Apologies for being suspicious of the email address, but for unknown reasons I get the error stated above.

Fwiw I have flagged @wavelabpro because that person or bot sent me a worthless PM. I still think that is a bot of some kind.

1 Like

After checking the crash dump, though I don’t know exactly the reason, this is related to the file view and the fact that you have a file selected in the file browser. Try quitting while hiding first the file view.
I could not reproduce.

1 Like

Yes, I did hide the file view, then quit and there was no crash. So this must be related to having the file view open?

With my normal template, I take advantage of 4 displays and usually keep them all open while working and then simply close everything when I’m done. Having that file view open, dispaly 3, causes the crash.

Conclusion, everything works as intended if I first close the file view.

Fwiw, this did not happen with prior WL versions. I could close all windows with no crashes. I’m pretty sure since I upgraded to WL12 that I have also closed this with no crashes. But in recent weeks, I have experienced this.

I will add a protection agains this issue, though, as I can’t reproduce it, I ignore if this will be effective.

1 Like