Subject:Re: SS 5.0 build 127e crashes processing XSLT Author:Minollo I. Date:21 Oct 2003 07:02 PM
The problem is caused by Stylus running out of memory. The source document
is fairly large (about 60MB in unicode), and the output is pretty large too
(about 22MB in unicode).
The main problem is caused by the size of the output document, which is not
handled in a scalable way in 5.0 BL127.
Processing works fine on my machine, but it does require a large amount of
virtual memory (VM) usage. The same processing against the new codebase we
have improved for the next 5.1 release takes half as much VM as BL127 requires.
We are investigating if backporting those changes to BL127 is feasible; if
it is we will make an update available. In the meanwhile you may want to
try raising the VM settings on your machine.
Subject:Re: SS 5.0 build 127e crashes processing XSLT Author:Minollo I. Date:22 Oct 2003 09:17 AM
At 08:02 AM 10/22/2003, stylus-studio-tech Listmanager wrote:
>...
>1) I have a very decent machine.
>It is Win2K Advanced Server 2000 SP3.
>It has 1 GB of physical RAM and configured to use 3 GB of virtual memory.
Then it's strange; processing with the built-in processor works smoothly on
my laptop (Stylus tops 450MB of VM)... .NET does have some problems, which
we are not sure yet if related to Stylus Studio or not.
>2) What is a time frame for the release of the SS v.5.1?
Early December, 2003.
But the possibility to make the improvement available as part of a 5.0
update is not ruled out yet.