[8.5.2 with Seaside] Debugging a callback sometimes hangs the image

But I also sometimes (well, several times a day) see a similar issue, that I think is unrelated to Glorp (but since it happens in the same codebase, I cannot be sure). 

From time to time, the image doesn't respond to HTTP Requests any more. You can use the Browsers and Inspectors and such, but the web browser (both from local and remote machines) never get an answer from the Seaside Image (it simply waits for a response for 20 minutes. I never tried any lounger). There is nothing obvious about CPU or memory utilization and you can work on code without any problems. The hang can happen at any place in the application, so I have not realized any pattern as to under which circumstances this whole thing happens.

When you stop the WASstServerAdaptor in such a situation, the Browser immediately displays an error. You can restart the Adaptor and all is good again (unless you have to start your test session from the beginning). The image may now work perfectly for hours, but it may occur after five minutes again.

The only pattern that I seem to see is this: it seems this never happens before you have used a debugger for fixing callbacks or render code. But I am not 100 % sure.

I luckily only see this effect in a development image, never in a packaged runtime, so I guess it is related to debugging...

I am using VAST 8.5.2 on XP and Win 7, but I had this in previous versions as well. I never paid much attention to it, because I got used to stopping/starting the adapter and git along with it quite well, but now I sometimes have long sessions to test stuff (10 or more pages to fill in), and this turns into a problem for me.

Has anybody else seen this happening? Did anybody try and hunt this bug? Any ideas what could cause this?

Joachim