Look, get yourself a big magnet, and run it over your hard drive whilst running Sonar.  You will make it crash.
 
You're just not trying hard enough.  :)
 
Bob Bone
 

musicroom
Do you guys see any changes in resources used from X2 projects running in X3? Reason I'm asking is I loaded a large X2 project into X3 last evening and I had to raise the buffer settings to play it. 

I haven't noticed anything other than when using Ozone, I no longer get memory spikes. It was never anything super serious but my CPU usage would jump about 8% or so every couple of seconds while running in X2. Engaging PDC would stop the spikes so I never really looked into it any further? With X3 I don't even have to engage PDC with that plug any more, so I'm guessing the overhaul of the VST engine deserves some glory?!!
 
So far X3 is solid as a rock! As I add a plugin the usage meter jumps accordingly but settles and remains quite constant. Melodyne tells me to raise the buffer while using it? I don't bother (haven't since X2) and I am yet to suffer any dropouts or glitches in playback or recording thus far.
 
Actually the only weirdness I have experienced? I talked about in the 'VST Scan Issue' thread. Where my browser wouldn't display producer effects if I clicked 'Default All Plugins.' It would display all instruments and all of my plugs but X3 plugs like compressors, the blue tubes etc. would only display if I had the browser set to 'X3 Producer Effects.' But as I stated in that thread, a close and re-open of X3 sorted it!
 
I must also add that as I have owned, Melodyne Editor, for quite some time now, I have never used v-vocal for anything other than a play around. I have seen a few threads where it looks like that plug is giving peeps grief for some reason. Has Gibson made the purchase yet? Can we flat out start blaming Roland for no other reason than the hell of it?...

robert_e_bone
Look, get yourself a big magnet, and run it over your hard drive whilst running Sonar.  You will make it crash.
 
You're just not trying hard enough.  :)
 
Bob Bone
 

 
My delusions of thinking I was a "magnet" have been shattered

ProjectM
Sounds good! I installed X3 yesterday and only played arounda  bit. Seems pretty stable so far. I'm have this thing I need to do with a deadline next monday so it will be interesting to do some stresstesting. So far, I'm really liking what I'm reading here though ;)

With X2 I've had a couple of seconds of the 'Not Responding' appear in the header on the odd occasion (mainly with heavy projects that were pushing my RAM.) But the program always came back online without having to close and nothing was lost or went haywire. It was smooth sailing all 'round!
 
After running a few large projects (large for me) and not being able to make X3 blink. I did what I stated in the OP to see if it would cause any weirdness. Streaming videos and doing multiple things on the net simultaneously, has been able to crash Studio One a couple of times. And though it's never fully crashed Cubase 7? I have had to close the song in app and re-open the song to get it going again. I realise those issues are more likely to be due to my PC nearing maxed, rather than a program problem? But I had to post when X3 stood staunch and unaffected. As if it were daring me to use more than my RAM limit?
 
Somewhere a (many?) producer(s) is (are) shaking his (their) head(s) at my habits...

@Royal Yaksman
 
Regarding you "Somewhere a (many?) producer(s) is (are) shaking his (their) head(s) at my habits..." post above, 
 
Don't sell yourself short - it's not just producers that shake their heads at you - us keyboard players do too - hee hee :)
 
Bob Bone
 

I crashed X3 by opening a Waves Renaissance comp VST3 as my first action after opening my (X2) project. After closing another (X2) project. No hang, just boom, exit, Sonar stopped working. Couldn't reproduce though.

If you open a VST3 version of waves after a VST2 waves plugin in the same SONAR session it will crash. This is a known Waves limitation.

I had my first crash. I opened LimiterNo.6 in the Pro-Channel and it wouldn't do anything, so I dragged it over to the fx bin. I stopped the playback, and hit play and it worked for about 10sec then crashed. I couldn't see a way to send a report ...everything has been fine since. I'm loving X3 so far!

Noel Borthwick [Cakewalk]
If you open a VST3 version of waves after a VST2 waves plugin in the same SONAR session it will crash. This is a known Waves limitation.

Both my projects were old ones from X1, so I didn't put in any VST3s unless Sonar auto-replaced them. I have't really tried to reproduce though.
But I'm more interested in the words "known Waves limitation", does that mean it's not considered a but?

robert_e_bone
@Royal Yaksman
 
Regarding you "Somewhere a (many?) producer(s) is (are) shaking his (their) head(s) at my habits..." post above, 
 
Don't sell yourself short - it's not just producers that shake their heads at you - us keyboard players do too - hee hee :)
 
Bob Bone
 

Yeah I'm kind of used to getting it from all directions.
 
I will however maintain 'til my grave, that bouncing stems is boring! Clearly I need the comedy channel on during it!!!