Just a quick thought - does you project have any hidden tracks with Melodyne on them?

I was going to bump this this morning but then it dawned on me to try Melodyne in a new project.
It worked fine so it must have something to do with the particular older project I was using.
 

So you guys get no crashes when opening in safe mode without Melodyne?

no. no hidden tracks with melodyne in them.
 
haven't tried shift opening without melodyne, but when Sonar crashes it says it's melodyne that caused the crash.

I have also had massive problems over the last 3 days, all involving melodyne, and all relating to timing changes. The only way I could stop Sonar from crashing, sometimes just halting and screens/computer completely frozen, was to open the projects involved, and delete the offending tracks completely. Once I have finished tracking, I save off and rename the project to begin all editing work, which the only way I have been able to backtrack and re-load the tracks, pre-melodyne.
 
I cannot provide further proof at this stage, as I was working with a new client, who was extremely un-impressed, and I was at a loss. I've not had any problems like this to date. For me, it's all since I upgraded to Melodyne Editor.
 
All latest upgrades to both PC, windows and software have been applied.
 
When I have time, I will look into the reports and try to get a handle on what's happening, but for me, this is a major issue and I will return to VV for timing related editing until I can figure it out. Right now, it's cost me dearly.

 For what it's worth, to reiterate what I posted a couple of days ago, I have also been experiencing some crashes, namely white-outs followed by Sonar X3e closing (on Windows 7, 64-bit after Sonar issuing a terse announcement that it is about to, in fact, close) while using Melodyne Editor. These crashes have all come while I was trying to use the tempo tool.
 
For what it's worth :)
 
 

I have not experienced any crashes myself but then I always split each song into about 8 clips.

I presume you meant split each 'track' in 8 clips Alex, or are you talking something different?
I do too. Usually only pick the small part of a track that needs correcting anyway, and then I have got into the habit of, once fixed, bounc to clip. Seems to me that if too many regions are created, SONAR struggles, so I try to keep the count to a minimum. I also save after every fix, because of the problems I've been having. But these last few days, saving didnt matter. The project would re-open, but any attempt to keep working, would cause a serious crash. As said before, if I removed the track entirely, things would be behave from that point on. Until the next 'fix'.
 
I'm not sure, but I think all of my problems are related to making timing changes, and depending how zoomed, differences in regions created within a track, of the 'snap too' setting. For example, One region altered with a snap too of say 1/4 and another region altered under 1/64. Manually changing things seems to cause havoc.
 
Just a guess at this stage, but that's what I'm feeling is happening.

It is interesting, MacFurse, that both of our problems seem to be timing-related. Of course, that may be only coincidence.
Maybe somebody more knowledgeable than me will be able to make some sense out of it :)

I'm not sure if it's limited to regions with timing changes. I have a feeling that it's just the creation of Melodyne regions themselves that cause the problem. The clips in my crashy project feature both pitch and timing adjustments. The problem is that it's very hard to reproduce an issue like this in a fresh project. Everything was hunky dory when I first created the regions and then after a long while of working on the project the crashes just started happening.
 
Incidentally I'm using Melodyne Editor too, but the clips in question are all using the melodic algorithm, not the polyphonic.