Thanks a lot for the information. I have one further question about
this problem that perhaps you could help clarify. My script does use
recursion to process the directories, so this could be my problem. The
error I receive is not "out of stack space" however. I am running Rose
on Windows NT and the error I receive is:
"Application Error: The instruction '0x77f64a3d' referenced memory at
'0x0ce4c155.' The memory could not be 'written.'"
Although this may be the same error, I was wondering if you knew for
sure that this memory is the stack.
-----Original Message-----
From: Andr� VEGA [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 17, 2001 1:13 AM
To: Knight, David (MED)
Subject: Re: (ROSE) script termination - memory limitations
Hi David,
Your problem and some others seem very well known...
I've recently run into "Out of stack space" while running a recursive
function
in a compiled rose script.
Hot line told me that compiled script are provided with a size of memory
2 or 3 times less
than an uncompiled script, that's why you run into memory problem with
the compiled version.
For trying to find some similar problems to yours,
go visit:
http://www.rational.com/support/technotes/index.jsp
Here is some workaround to try to solve your problem, given by support:
1) Some Code needs to be rewritten to avoid the deep recursion in
the program. (that does not seem to be your case)
2) Not a fix but a way to get further along is to increase stack
space by running the file as a .ebs as oppossed to .ebx from
menu. This will get you 2 or 3 times further before hitting stack
limit as oppossed to if you run the ebx file directly. There maybe
some other speed issues since you are now running .ebs, but that's
the trade off.
(that could help: try to split your script, and call other .ebs script
as you need them,
do that using RoseApp.LoadScript(...ebs) and then RoseApp.Freescript for
freeing
memory ressources after having used the script, use as many global
cvariables as you can,
for string or string arrays for example, which eat a lot of stack memory
)
3) Put parts of the script in a VB component and use it from the
script.
You may want to rearchitect the integration by extracting some
of the logic and placing it in a COM client to Rose since this is
the most scalable solution.
(that could help, I have not tried this)
4)
Fully port to visual Basic
You have the option of creating an Addin or script with VB and porting
the Rose Script code to VB.
(that could help, I have not tried this)
for recursion problem, have a look at
http://www.rational.com/technotes/rose_html/Rose_html/technote_12194.htm
l
good luck, Andr�,
--
------------------------------------------------
Andr� VEGA
[EMAIL PROTECTED]
01.46.08.63.27
------------------------------------------------
************************************************************************
* Rose Forum is a public venue for ideas and discussions.
* For technical support, visit http://www.rational.com/support
*
* Admin.Subscription Requests: [EMAIL PROTECTED]
* Archive of messages:
http://www.rational.com/products/rose/usergroups/rose_forum.jtmpl
* Other Requests: [EMAIL PROTECTED]
*
* To unsubscribe from the list, please send email
*
* To: [EMAIL PROTECTED]
* Subject:<BLANK>
* Body: unsubscribe rose_forum
*
*************************************************************************
