OK, just received this error . I'm just wondering if it the famous OOM error. I was trying to save work I had just completed within the software and in the middle of saving this error box pops up. When it returns to the 3D display mode I have duplicate white only cabinets that are about 1 1/2 times bigger than the normal cabinets placed inside and outside the room walls. I had no success in saving the data at all, I tried deleting the newest added cabinets to see if it would save after I found the bad cabinet but I got back farther then when I started and still got the OOM error. I assume this id the dreaded error. I am still using V5 and waiting for the bugs to be resolved in 5.1 and 5.2
Sorry, kinda chicken. I like to wait until most of the bugs have been worked out. I'll get there soon though. So, is it the same OOM message that I have seen here?
You shouldn't be chicken because version 5.1 build 2 has worked out some of the bugs. So it should be better already. Since I haven't seen the 'out of memory error' yet I wouldn't be able to answer your question.
Jean-Gabriel Voyer
Janot Interiors Ltd www.customcabinetscalgary.com
Dell Precision PWS490, Intel Xeon CPU,3.00 GB Ram, Window XP Pro, Quadro Fx 3500
I to have been getting the OOM error but only on files created in 5.0 and only when making to many changes before saving. I beleive this is an issue with not saving often enough. Try going back and changing maybe 3 cabs and then saving.
Leo,
I just checked and Version 5.1 build 2 has corrected the Out Of Memory error on my job that started that whole thread. I don't think the Out of Memory thing is fixed but it will be better in 5.1 build 2 than it is in 5.0 build 12.
Kerry
I have a simple room layour with seven copies of the same base cabinet...nothing special at all.
If I take the entire layout to the line drawing editor, memory usage goes up to 1.6GB! The job file is only 17.9MB. If I try to copy the room in the LDE, it will churn for a while and finally cough up the out of memory error then crash.
This is with 5.1 build 2 and the room and cabinets were created with 5.1.
I do know that some memory issues were corrected with 5.1 build 2 and that the programmers are still working on other issues. I sent Scott Vaal the job and lots of information from my observations with the job.
DanEpps wrote:I have a simple room layour with seven copies of the same base cabinet...nothing special at all.
If I take the entire layout to the line drawing editor, memory usage goes up to 1.6GB! The job file is only 17.9MB. If I try to copy the room in the LDE, it will churn for a while and finally cough up the out of memory error then crash.
This is with 5.1 build 2 and the room and cabinets were created with 5.1.
I do know that some memory issues were corrected with 5.1 build 2 and that the programmers are still working on other issues. I sent Scott Vaal the job and lots of information from my observations with the job.
If you wanna have some real fun (others should probably ignore this, I think only Dan and I would find the fun in it) set up Windows Task Manager and open the I/O Write Bytes column under the Processes tab. It'll make your eyes bug how much and how quickly that total rises by what you would THINK is a 'simple' process within eCabs. The cumulative effect of keeping the software running without restarting it every once in awhile - as well as Windows itself - makes one start to design cabs/projects differently so as not to tax the system until it's absolutely necessary.
I seem to have overcome the problem to a small taxing degree. I start by creating a room with walls and saving it twice calling one of them walls. I open the other file and start my design. Once I have my room basics I make the adjustments to the cabinets. I then take each cabinet to the editor and save it. now I open the walls file reinstall all the saved cabinetry into the room. This time I click save file as and click on the other file and replace it.
I have determined that resizing the cabinetry has influenced a breakup in the positronic membraine inhibiting the optiminal co-processor. Thus resulting in a catastrophic event. Nonetheless an abrupt end to a seemingly smooth process.
. I'm just wondering if it the famous OOM error. I was trying to save work I had just completed within the software and in the middle of saving this error box pops up. When it returns to the 3D display mode I have duplicate white only cabinets that are about 1 1/2 times bigger than the normal cabinets placed inside and outside the room walls. I had no success in saving the data at all, I tried deleting the newest added cabinets to see if it would save after I found the bad cabinet but I got back farther then when I started and still got the OOM error. I assume this id the dreaded error. I am still using V5 and waiting for the bugs to be resolved in 5.1 and 5.2
