I didn’t see it listed in the 1.19 current beta file list but it seems like with stable 1.19 that right clicking the floating box(Status box) crashed bitcomet. If its confirmed from others i guess I’d need to submit.
I am using vista sp2 pro (all updates). I don’t think you’d need my connection type and speed etc., so I didn’t add them.
My luck is I had shutdown after download complete on and exiting confused something since I did see Bitcomet exits slower when I did have auto shutdown and exit the floating box.
Bitcomet had been running for a maybe an hour with the setting on before shutting down by the method above.
I’m attaching what I think is the crash log.CRASHLOG.TXT
BitComet caused an Access Violation (0xc0000005)
in module BitComet.exe at 001b:00435e94.
Exception handler called in Exception_Debuger.
Error occurred at 3/18/2010 22:57:26.
F:\BitComet\BitComet.exe, run by aPerson.
Operating system: Windows Vista (6.0.6002).
2 processor(s), type 586.
47% memory in use.
2048 MBytes physical memory.
1616 MBytes physical memory free.
4096 MBytes paging file.
3144 MBytes paging file free.
2048 MBytes user address space.
1856 MBytes user address space free.
Program name: BitComet
Process execute time: 0 day 0:34:4
Program status: Exit
Program mode: download
Socket init version: v2.2
web frame:
msg id: 275
piece cache size: 0
bt mem_block_size: 0
crash info:
debug info:
pool_block dump:
allocated_size = 0
allocated_list_size = 0
free_block_size = 0
free_block_num = 0
commited_size = 0
notblock_size = 0
notblock_number = 0
total_size = 0
Read from location 00000020 caused an access violation.
Context:
EDI: 0x02801018 ESI: 0x00000000 EAX: 0x0012ec24
EBX: 0x00000000 ECX: 0x00435f85 EDX: 0x775b5e74
EIP: 0x00435e94 EBP: 0x0012ec50 SegCs: 0x0000001b
EFlags: 0x00050246 ESP: 0x0012ec10 SegSs: 0x00000023
Bytes at CS:EIP:
8b 43 20 3b c6 74 0e 56 56 68 08 03 00 00 50 ff
Stack: [ignore]
Module List: [ignore]
===== [end of CRASHLOG.TXT] =====
CRASHLOG.TXT (2.71 KB)