I don't know if anyone else has ever noticed this (or if anyone can replicate it) but if I launch C::B and load a reaonably large session/workspace (this one happens to contain around 25 individual projects) C::B hogs my processor for around 4-5 minutes, taking up 100 percent of the processor cycles. After 5 minutes or so, it settles down. I'm using the Windows version downloaded maybe 2 months ago. Anyone else ever seen this? What could it be doing?
