Are you sure it's "freezing"? Does windows give the [program doesn't respond] tag thing?
You could try to (manually, so not using windows-d or similar shortcut) minimizing all other programs; I had something similar before with another program, and that way it'd be accessible again. Might be that it's not really a C::B bug, but more of a annoying combination of circumstances?