w00t! What caused the problem?
spasm itself.
If you do some glitchy source code that leads to a loop (macros or bugged code), spasm keep running forever and the server keep you waiting but you never get the resulting page. Even if you close the page on web browser the server is still executing spasm... Spencer could add an optional timeout to spasm next version that I could use.
Now imagine dozens of spasm running, you get a problem on your server.
I will manage a way to let you terminate all instances of spasm but if someone sends bad code, he will not get an answer from the server.