#19 Core doesn't quit when burst is "closing" it

[Anonymous]

When burst is set to stop seeding after a certain ratio
is reached, it attempts to quit the btheadless core
when that ratio is reached. The GUI says "Closing...",
but when viewing the DOS screen for the transfer, in
many cases the transfer keeps going and the download
does not close. I can manually quit the transfer in
the DOS screen by pressing "Q"...when I do this the
transfer closes properly, and the transfer is properly
removed from the burst GUI.

This can become a severe problem when operating with
auto-queue. When a transfer starts closing, the next
transfer in the burst queue is started. But if the
previous transfer actually doesn't quit, you end up
with more active transfers than you wanted. Eventually
more and more transfers start up without the previous
ones quitting, taking up all RAM/CPU, and finally
crashing the burst GUI (but leaving all those
btheadless processes running, so the computer is still
swapping like crazy).

I suspect this problem is caused by the btheadless core
"missing" the Q key event being sent to it from the
burst GUI. Perhaps it would be better to send a "Q"
key event every 5 seconds to the core, until it finally
quits.

I am running burst 3.10b with core 1.1.4 (the latest
versions as of today) under XP pro SP2. I am not
running it under 98/ME emulation mode. This is a
P3/800 machine with 512 MB RAM.

[Andrew Denman]

Logged In: YES
user_id=1080607

Don't know if this is related, but it does the same thing
when it tries to close paused downloads when you quit burst
(although it doesn't continue swaping - it's paused). The
GUI then just sits there and doesn't quit.

P4M, 512MB, XP Pro SP2, No emulation

[Mike Ravkine]

Logged In: YES
user_id=831271

This is a known problem, windows sometimes drops my quit
message.

It will be fixed in the next release, but don't hold your
breath.