Alloc and Expand

[velasquez]

Somebody can me to say the functions alloc and expand, they help in the administration of memory with a big project of OpenDCL. 
To help her, which the best values?

Thanks

[velasquez]

Does anybody have some information on my question?

My program interrupts AutoCAD after you vary calls in some computers.

[Fred Tomke]

Hi vela, how are you?
I must say that I don't know both of these two functions. And I have no memory problems with my forms.
But I must say that I do not continue keeping all my forms in one project: when I had started converting all forms from ObjectDCL to OpenDCL it started to split them by modules or classes. My old ObjectDCL project had a filesize of nearly 2 MB and needed a recognizable time for loading at runtime.
I'm not sure if I already have recommended you not to keep the images within the file but loading them at runtime. I have a form where I was forced to store them into the project file. But then the loading time increased heavily. That's why I keep them separarily.

That's the only thing I can tell you.

Fred

[velasquez]

Hello Fred, 
Me I am well. 
My project of OpenDCL has 1,5 MB of size. 
All the images are files PNG and they are part of the project. 
The work goes well until that some thing drops AutoCAD.

[Fred Tomke]

Hi, vela, my problem is that I can't reproduce this. In the past I haven't discovered any memory leaks. Finding out the reason would be like fishing in clouds.

Fred

[velasquez]

Hi Fred, 
As soon as the mistake to happen I send the error messages for you. 
Thanks.

[velasquez]

Hi, vela, my problem is that I can't reproduce this. In the past I haven't discovered any memory leaks. Finding out the reason would be like fishing in clouds.

Fred

Hi, Fred,

See the error messages. 
They price after many calls of my program. 
Command: pam 
_.opendcl 
Command: APPLICATION ERROR: bad VLisp request: #-32737 
APPLICATION ERROR: bad VLisp request: #-32764 
APPLICATION ERROR: bad VLisp request: #-32763 
APPLICATION ERROR: bad VLisp request: #-32761 
APPLICATION ERROR: bad VLisp request: #-32760 
APPLICATION ERROR: bad VLisp request: #-32746 
APPLICATION ERROR: bad VLisp request: #-32746 
APPLICATION ERROR: bad VLisp request: #-32746 
APPLICATION ERROR: bad VLisp request: #-32746 
APPLICATION ERROR: bad VLisp request: #-32746 
APPLICATION ERROR: bad VLisp request: #-32746 
APPLICATION ERROR: bad VLisp request: #-32755 
APPLICATION ERROR: bad VLisp request: #-32754 
APPLICATION ERROR: bad VLisp request: #-32740 
APPLICATION ERROR: bad VLisp request: #-32740 

[Fred Tomke]

Yes, vela, I can remember this. But I had this with ObjectDCL. And it was so long ago that I cannot remember what it was caused by. Maybe there are endless nested loops (I mean effects where functions are called which invokes events that the same function call again)?

Fred

[velasquez]

Yes, vela, I can remember this. But I had this with ObjectDCL. And it was so long ago that I cannot remember what it was caused by. Maybe there are endless nested loops (I mean effects where functions are called which invokes events that the same function call again)?

Fred

Hi Fred, 
I didn't get to find this condition. 
The program works very well for a lot of times and then he/she appears the problem, when he is carried. 
When the program this compiled in .VLX the problem it provokes a crash in AutoCAD.