Mac Forum / Programming / CodeWarrior / April 2005

This is with CW 9.4.

Sometimes, for reasons I don't know, CW goes into a mode where it
activates extended "Caching..." sessions every time I save a change to
a file. When this happens, CW is unresponsive until it completes the
caching process. Given that I save habitually, this seriously affects
my productivity because I end up spending so much time waiting for the
caching to complete.

It obviously a bug in CW, and normally saves happen very quickly, but
apparently on occasion something gets out of whack in CW and this
starts happening. When it *does* happen, the only way to fix it is to
quit CW and relaunch. However, the sequence of events seems to be:

- Press Command-S.
- Caching begins.
- Caching completes.
- File is finally saved.

This is annoying, but here's the serious bug part: If I use Command-Q
to quit CW during the caching process, the caching is eventually
aborted and the application quits, but any unsafed changes don't get
saved. I've lost newly written code I was trying to save on at least
two occasions recently, and that makes me an unhappy camper.

Is this a known issue? Any chance it will be fixed?

Larry