After working with CS3 for a couple of weeks, here is a summary of definite problems I have run into:
1) Memory leakage: The CS3 apps fragment memory at a fast clip. After a couple of hours of normal production work with PS, IA and ID I can recover more than 500MB of RAM using a memory defragger. (The record so far is 856MB.) Workaround is to shut down the apps and run the defragger every two to three hours.
2) Bridge interacts with PS, ID and IA in some unknown way to hang vector copy/paste. Copying a path to the clipboard in InDesign, Photoshop or Illustrator hangs the app until Bridge is closed. There is no problem if Bridge is not running. Workaround is to either keep Bridge shut down or close it if you run into a hang. The problem does NOT manifest copying text or pixel data, as far as I can tell; only vectors. It also only seems to affect clipboard copying. Alt-drag copying is not affected.
3) The "Recent" function in Explorer is not accessible from the Adobe dialog in any of the apps, which is unfortunate as it's extremely useful. Currently I flip back and forth between the Adobe dialog and the OS dialog, according to whether I need the thumbnails or want to navigate to a recently used folder.
4) Favorites in Bridge do not show up in the Adobe dialog in any of the suite apps, a serious omission from the CS2 version. I don't know if this is a bug or a deleted feature. (If the latter: shame on somebody!)
5) Accessing a Version Cue project requires Bridge to be running. InDesign will crash hang when opening a Recent File that is in a Version Cue project if Bridge CS3 is not running.
The only other comment I can throw in here is that the faster load time promoted for Photoshop CS3 doesn't seem to manifest in a Vista environment. There may be a marginal improvement, but it's not significant. Illustrator remains very slow to load and to close, although it is much, much nicer to work with than earlier versions and does run faster.
I'm posting this for general info and in hopes it helps the engineering folks track down the bugs. The memory leakage and vector copy issues are surprising. The seem very large to have slipped through beta testing undetected.
1) Memory leakage: The CS3 apps fragment memory at a fast clip. After a couple of hours of normal production work with PS, IA and ID I can recover more than 500MB of RAM using a memory defragger. (The record so far is 856MB.) Workaround is to shut down the apps and run the defragger every two to three hours.
2) Bridge interacts with PS, ID and IA in some unknown way to hang vector copy/paste. Copying a path to the clipboard in InDesign, Photoshop or Illustrator hangs the app until Bridge is closed. There is no problem if Bridge is not running. Workaround is to either keep Bridge shut down or close it if you run into a hang. The problem does NOT manifest copying text or pixel data, as far as I can tell; only vectors. It also only seems to affect clipboard copying. Alt-drag copying is not affected.
3) The "Recent" function in Explorer is not accessible from the Adobe dialog in any of the apps, which is unfortunate as it's extremely useful. Currently I flip back and forth between the Adobe dialog and the OS dialog, according to whether I need the thumbnails or want to navigate to a recently used folder.
4) Favorites in Bridge do not show up in the Adobe dialog in any of the suite apps, a serious omission from the CS2 version. I don't know if this is a bug or a deleted feature. (If the latter: shame on somebody!)
5) Accessing a Version Cue project requires Bridge to be running. InDesign will crash hang when opening a Recent File that is in a Version Cue project if Bridge CS3 is not running.
The only other comment I can throw in here is that the faster load time promoted for Photoshop CS3 doesn't seem to manifest in a Vista environment. There may be a marginal improvement, but it's not significant. Illustrator remains very slow to load and to close, although it is much, much nicer to work with than earlier versions and does run faster.
I'm posting this for general info and in hopes it helps the engineering folks track down the bugs. The memory leakage and vector copy issues are surprising. The seem very large to have slipped through beta testing undetected.