Startup crash using 2018.09 build 29 - anyone else?

I've been using CbB since 4/8 and started using 2018.09 build 29  4 days ago. I just booted the computer up and double clicked on a CWP file from yesterday that I opened and closed more than once yesterday.
 
Today it crashed CbB on startup with the familiar error screen from CbB. It was one of those crashes that required a reboot. After the reboot it opened this CWP file fine, I then closed CbB and tried again and it opened. So this is clearly intermittent, but still unnerving to cause a reboot.
 
This is the 1st time I've had this happen with CbB. I realize that build 25 had this bug, so I didn't install it, but build 29 is supposed to fix this bug. 
 
So has anyone else had this same problem?

Noel Borthwick [Cakewalk]
If you have a dump file send it to me and we can see if its a different cause.

 
I just sent it as a PM to you
DMP was 3064 KB. The limit is 3000, so let me know if you got it - thanks,

Nevermind - I was going to suggest the "Hotfix" but you already have it.

jgarland
Yes, it is happening with me. I am on the same Cakewalk version. I believe it is related to the toast notifications.
 
Steps to re-create, and this is repeatable every single time.
1. Launch Cakewalk and click to open a project while the Plugin scan and toast notifications are still running.
2. The project will open and then Cakewalk will immediately crash.
 
After disabling toast notifications in preferences:
1. Launch Cakewalk and click to open a project while the plugin scan is still running.
2. The project opens and all is OK - no crash occurs.
 
As I said, I can repeat this every single time via enabling and disabling the toast notifications.

Excellent detective work here!  I reported it to BL.  They will fix it!

I didn't get your dump file. Please put it on some file sharing service and pm me the link.

@gmp - do you have "Rescan All Plugins" and "Scan in Sandbox" checked with "Scan on Startup" selected?
 
This might be a dangerous combination, especially if your project is trying to load a VST currently being scanned in the sandbox.
 
Personally, I almost never have "Rescan All Plugins" checked, and I now have "Manual Scan" selected. I do a manual scan any time I install a new plugin.

Noel, steps for clearing picture cache?
 

Thanks, scook. I have a couple of projects that play, but visuals behave oddly. (virtual meters don't move). I'll bet something like thiis could be the culprit.
 

Noel Borthwick [Cakewalk]
FWIW I just added defensive code to prevent this specific rare crash from happening again.

Super news!  After that crash requiring a reboot I decided to go back to 2018.07, but now I'll go back to using 2018.09 and see if it happens again. Since 2013 I've had a macro that deletes the complete pic cache at 11 pm, so any corruption there was deleted. Thanks for figuring the cause of this. I'm looking forward to having the defensive code in the next release.

jgarland
Further investigation:
Deleting the picture cache did not fix the crash (I know this wasn't meant for me but I gave it a shot anyway).
 
Cakewalk still crashes if project opens while toast notifications are running - BUT - if I let the notifications completely finish, and then click to open the project, there is no crash. 

It seems like what you're saying is that you're double clicking on a CWP while the toast notifications are running. I assume when you open CbB it's loading a template or a song by default and while that is loading you're double clicking on a different CWP because that's the one you want to work on.
 
What I do is while CbB is closed, I double click on the song I want to work on and then it opens CbB. Hope this helps

Noel,
sent the file via PM.

I keep a backup of all the previous versions, by copying the "Cakewalk Core" directory within c:\program files\Cakewalk and renaming it:
 

 
That way I can run the "Cakewalk.exe" from within each directory to run an earlier version.
 
I'll PM you a download link for my backup of 2018.07.

Yes, it would be a nice feature. But I'll manually perform the task from now on... I'd also like to add, that when this began, I posted and was contacted by a Mr. Sassor, I believe. After sending him a crash dump I was told that Melodyne was the culprit, and that I needed to contact them for a resolution, even tho Melodyne had not at that time changed. Blaming Melodyne was bum information, as I've got the problem explained here, but ended up chasing my tail on this because I was misinformed. Yes, I am a tad bent out of shape!!!