I was debugging an XSLT when I realised I would have to debug a different XSLT that generated its source file.
So I simply shut down Stylus in the middle of the debugging session to free up the 1Gb it had consumed (because of the memory leak problem you guys found with the xsl:key). The whole application window disappeared. Then I got the dialog box asking me if I'd like to go to the line where execution had been stopped on. I clicked 'no' and then got the usual notice about sending in the log.
> this is a known issue. Stylus doesn't
>appreciate being shut down during XSLT
>debugging.
In the second instance I had already whacked the cancel button several times, but Stylus hadn't cancelled the execution within my usual waiting limit of about 2 minutes.
>We'll address this problem eventually.
Eventually! Argh!
The Stylus XSLT processor is obviously a different thread, maybe it needs to become an independent process. That way it will be visible (and killable) through the Windows Task Manager - that's how I stop an XSLT that's been going on too long when it's running under MSXML.
Subject:Re: SS4.6 103s: Crash - Exiting stylus while debugging Author:Minollo I. Date:22 Apr 2003 08:59 PM
>...
>The Stylus XSLT processor is obviously a different thread, maybe it needs
>to become an independent process. That way it will be visible (and
>killable) through the Windows Task Manager - that's how I stop an XSLT
>that's been going on too long when it's running under MSXML.
Hitting the Cancel button will make it, even if you can experience a bit of
delay if you are computing a long XPath expression.