I use Abyss on my laptop as a development environment for my PHP-based projects. When I run Abyss in a terminal, with no command line arguments, everything works just fine. That is, until I'm done working for the time being and try to terminate the server by hitting Ctrl+C.

~$ ./abyssws/abyssws
Abyss Web Server X1 (v 2.6)
Copyright (C) Aprelium - 2001-2009

-- Default host on port 8000 is up and running (Local URL http://127.0.0.1:8000)

Console local URL: http://127.0.0.1:9999

Signal #2 received. Shutting down the server...

And then it just sits there, without returning to the shell. I try Ctrl+C again, but no dice. I'm forced to launch gnome-system-monitor and kill the abyssws process, at which point an error message is echoed to the terminal and I'm finally back at a shell prompt.

Critical: The server died unexpectedly (code=0xFFFFFFFF), it is being restarted automatically.
~$

I should probably note that two instances of abyssws appear in the system monitor when I run the server. The only difference being one has a few command line arguments. "abyssws --slave --interactive" is the one I have to kill for the terminal to return to the shell, and when I do that, the other instance dies. However, another one is somehow spawned and remains open even after I close the terminal window.
This only happens after I've been working on a project, so I think it may somehow relate to PHP. It does not happen if I run Abyss with "abyssws --daemon" and use "abyssws --stop" when I'm done using it.
Has anyone else encountered this problem? It's not really a critical issue, but I felt I should post about it here anyway.