EM2 Crash "Exception: EXC_BAD_ACCESS" (Mac)

My Expression Media 2 crashed yesterday and generated a report (excerpt below). I've never seen this type of crash before in the 5+ years I've been using EM/iView. I submitted the report to Technical Support, but all they can do is forward the report to R&D.

Has anyone else experienced this type of crash? Is it possible to ascertain the cause of the problem from the report log? If so, can the problem be corrected?

Additional info: My catalog file (46 MB) is on my system hard drive while my images (8,600 images, 149 GB total) are on an external Firewire drive (Lacie 1 TB). This split arrangement is relatively new (about 1 month); I previously had everything on my system drive. I use only embedded previews to help keep the catalog small.


Microsoft Error Reporting log version: 2.0

Error Signature:
Exception: EXC_BAD_ACCESS
Date/Time: 2010-11-10 20:16:58 -0600
Application Name: Expression Media 2
Application Bundle ID: com.microsoft.expressionmedia2
Application Signature: IVW5
Application Version: 2.0.2
Crashed Module Name: QD
Crashed Module Version: unknown
Crashed Module Offset: 0x000098f8
Blame Module Name: QD
Blame Module Version: unknown
Blame Module Offset: 0x000098f8
Application LCID: 0
Extra app info: Reg=English Loc=0x0000

[... thread details omitted...]

Operating System Information
Operating System: Mac OS X 10.4.11 (Build 8S165)
CPU: G5 (970), Number: 2, Speed: 2147 MHz
gestaltPhysicalRAMSize err = 0, result = 2047 MB
gestaltSystemVersion err = 0, result = 0x1049
Screen: 1280 x 1024, depth = 32, ltbr = 0, 0, 1024, 1280

Microsoft Application Information:
Error Reporting UUID: 0FF003E2-5AF1-11DB-B91E-000D935714D4
Time from launch: 4 hours, 32 minutes, 2 seconds
Total errors on this client: 37