I never had problem there before, but the test harness debugging now seems like taking a while to do anything...
It is now idling all the time, with longest time (about 10 minutes) when stepping over a require() instruction (those required modules contain only functions, nothing immediately executable).
I'm using the "preview" service, and I know my internet connection is not awesome. It never has been more than a marginal issue however.
Also, the response time is still quite fast and normal when all debugs are un-checked and only the response is shown.
Could it be related to the last platform Release 4 days ago? I haven't used the test harness extensively since then.
I'll try again tomorrow and let you know how things are.
Just wanted to say that the issue seem to be resolved since your latest platform release.
Thanks a lot!