Issues with .RX2 files.

I was using X3b and previewing some loops from loop masters that use the .RX2 extension.  After switching from loop to loop and listening to the previews, Sonar would white screen.  Are there any known issues with this file type. My wave loop files do not exhibit this behavior. (White Screen, Sonar stops responding). Any body seen this? Thanks.

Fog
can't imagine Noel and co would have done much change with the rex2 side of things due to it being props library they are calling from.
 
don't have x3 , but maybe it is related to other things e.g the browser itself they need to look into.
 
 

Hmm... Fog you make an interesting point.  What I mean is I have a dual monitor setup with the Browser and CV undocked to the 2nd monitor.  Prior to this I reported an issue where if CL is in the master bus and CV is undoced to the 2nd monitor and I switch from track to track back to the master bus in that view Sonar will crash. If I do the same thing with nothing undocked ... no crash. (CWBRN-20140)
I will try the same with this condition with everything docked to see if I can replicate.  Maybe there is something going on when the modules are undocked. The bad thing about this is that I never get the crash report option to send to Cakewalk.  Just a white screen that sits there and taunts me. 
 
Any other good folks out there working wiith .rx2 files and multiple displays? What's your experience?  These loops came from Loopmaster if that adds anything.
 
 With that said ... Thanks for the idea Fog....

stevec
FWIW, if you're white screened (SONAR hangs) you should be able to use Task Manager to force an exception.  I'm not sure how useful the resulting dump file might be to CW but perhaps better than nothing!
 

Thanks Stevec. I will try that too!

Not sure if my case is relevant here, but recently I noticed some odd mouse icon shaking behavior when loading .rx2 files, which took a little while to load with a message "Building audio transients" in the transport module. I posted on the forums and Noel's answer was "REX files need to be imported internally before we can preview them since its not a native file format. The display is showing the normal process that happens when you import a rex file..." Another issue was that some .wav files were taking time to load. He suggested defragging the disk, which actually did help.