DW CS4 quits unexpectedly - Fireworks issue?

Question

Greetings,
I am using DW CS4 build 4117 on a mac pro with OS X 10.5.7
On about four occasions over the last week, DW quits unexpectedly and it doesn't seem to be related to anything in particular.  It can just be sitting there idle.  Have tried deleting the user cache file, which some forum posts suggest can get corrupted and cause problems.  The crash report always contains a reference to dreamweaver and ImageManipulator:Clipboard at Thread 1, and then at Thread 0 when the crash occurs there is a reference to Fireworks setting the image source from the clipboard (below).  Fireworks is not even running.
I am not an expert on decipering crash reports and an sort of new to the mac in general, so any help or insight you can provide will be greatly appreciated!
thanks!
- Gregg
Thread 0 Crashed:
0   Fireworks                         0x04cde9b1 FWImaging::SetSourceImageFromClipboard(unsigned short**, unsigned long&) + 735 (FWImaging.cpp:1016)
1   com.adobe.dreamweaver-10.0        0x00954986 ImageManipulator::ClipboardContainsImageData() + 62
2   com.adobe.dreamweaver-10.0        0x0041b495 JSObjDreamweaver::canClipPaste(JSContext*, JSObject*, unsigned int, long*, long*) + 163

Answer 1

Wanted to provide an update on what I have noticed since the original post.
I tried upgrading to Snow Leopard but that was a complete disaster as virtually nothing was stable.  There was the usual finger-pointing by both Adobe and Apple, but that's another issue.
I ended up having to completely wipe the drive and do a clean install of OS X 10.5.8.  So what I have now is an almost-new Mac Pro with virtually nothing on it except the Adobe Master Collection and some printer drivers.
And here's what I've noticed about the problem with Dreamweaver quitting unexpectedly:
It happens after I have inserted a thumbnail image into a table cell and then modify the image with Photoshop.  I always know when the crash is about to occur because of the way the scrollbars begin to behave.
So for example, I may insert an image that is 250x160, make a link to it, add a border, etc., and everything is great.
Then I decide to crop the image to 250x150 and do so in Photoshop. Dreamweaver will then begin show a latency in almost any menu action.  The scrollbars slow...to...a...crawl.  At this point I know it's about to crash, just like when you know your cell phone is about to ring from hearing the speaker interference.  And then <blip> Dreamweaver quits.
The workaround I have devised is to simply not edit any images unless I delete them from the page first.  Then I have to re-insert them, re-do the link and border, etc.  This is not the way it's supposed to work but Adobe does not seem to have a real solution.
There is another related post on Dreamweaver crashing (http://forums.adobe.com/message/238854) that noted the same entries on the crash report as I have been seeing:
Thread 0 Crashed:
0   Fireworks                     0x04cde9b1 FWImaging::SetSourceImageFromClipboard(unsigned short**, unsigned long&) + 735 (FWImaging.cpp:1016)
I'm starting to suspect some sort of end-of-file error is created when a source image is changed, but that's just a guess.