C-Command Software Forum

SpamSieve crashes under heavy loading

Twice within a few minutes, while Mail.app was chugging through about 1500 new IMAP messages, SpamSieve crashed. I’ve attached a backtrace from the offending thread below. Any ideas what might be happening? Thanks,

kobi

Process: SpamSieve [747]
Path: /Applications/SpamSieve.app/Contents/MacOS/SpamSieve
Identifier: com.c-command.SpamSieve
Version: 2.7.1 (2.7.1)
Code Type: X86 (Native)
Parent Process: launchd [160]

Date/Time: 2008-10-09 16:36:09.152 -0700
OS Version: Mac OS X 10.5.5 (9F33)
Report Version: 6

Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000004
Crashed Thread: 0

Thread 0 Crashed:
0 com.c-command.MJTDatabase 0xc2007f37 fileBtreeKeyCompare + 50
1 com.c-command.MJTDatabase 0xc2030e6f sqliteVdbeExec + 17384
2 com.c-command.MJTDatabase 0xc2032fcd sqlite_step + 83
3 com.c-command.MJTDatabase 0xc2018dfe sqlite_exec + 185
4 com.c-command.MJTDatabase 0xc2001e7e -[MJTDatabase commit] + 539
5 com.c-command.SpamSieveF 0xc903200d -[History commit] + 71
6 com.apple.Foundation 0x96e5164d __NSFireDelayedPerform + 477
7 com.apple.CoreFoundation 0x92f69b45 CFRunLoopRunSpecific + 4469
8 com.apple.CoreFoundation 0x92f69cf8 CFRunLoopRunInMode + 88
9 com.apple.HIToolbox 0x94eb7480 RunCurrentEventLoopInMode + 283
10 com.apple.HIToolbox 0x94eb7299 ReceiveNextEventCommon + 374
11 com.apple.HIToolbox 0x94eb710d BlockUntilNextEventMatchingListInMode + 106
12 com.apple.AppKit 0x93a2c3ed _DPSNextEvent + 657
13 com.apple.AppKit 0x93a2bca0 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 128
14 com.apple.AppKit 0x93a24cdb -[NSApplication run] + 795
15 com.apple.AppKit 0x939f1f14 NSApplicationMain + 574
16 com.c-command.SpamSieve 0x00001f8e _start + 216
17 com.c-command.SpamSieve 0x00001eb5 start + 41

SpamSieve’s statistics database was corrupted, perhaps due to a crash or disk error. Please try holding down the Command and Option keys when launching SpamSieve and then click Reset History.

Thanks for the fast response, Michael. Have reset history as recommended, and so far so good. Cheers,

kobi