long time to create windows after first instance
Posted: Tue Feb 20, 2007 10:07
Hi,
I have seen a similar post to this in the past, but cannot find the topic on the forums through search, so here goes...
I have an embedded Linux based system using Ogre 1.2.5RC1, and CEGUI 0.4.1. The OS runs from RAM. I have recently upgraded the embedded platform to this from previously running Ogre 0.15.2 and CEGUI 0.2.1 (If I remember rightly!). Everything working fine, except that the same system seems to eat a huge amount of RAM now when the CEGUI stuff is created compared to the old system. OK - I can work around this - but the best way to do so is to make certain rarely used GUI screens dynamic.
When they are created the first time, they are instant. Then everytime thereafter they take an age to create. Doing the same thing on the 0.2.1 system does not suffer with the same problem!! This is also true for the windows based platform where all the dev work is done.
I have introduced cleanDeadPool() to the destruction of these "dynamic" windows, but it doesn't seem to free up the memory. I have a large number of text boxes showing "results" of the game running, and these require a huge amount of RAM. - when the game resumes after they have been destroyed - there is insufficient RAM to continue running.
I am working through the system code now to see if there is anything else - but there are certainly the above issues with the system.
Any thoughts anyone?
Cheers
I have seen a similar post to this in the past, but cannot find the topic on the forums through search, so here goes...
I have an embedded Linux based system using Ogre 1.2.5RC1, and CEGUI 0.4.1. The OS runs from RAM. I have recently upgraded the embedded platform to this from previously running Ogre 0.15.2 and CEGUI 0.2.1 (If I remember rightly!). Everything working fine, except that the same system seems to eat a huge amount of RAM now when the CEGUI stuff is created compared to the old system. OK - I can work around this - but the best way to do so is to make certain rarely used GUI screens dynamic.
When they are created the first time, they are instant. Then everytime thereafter they take an age to create. Doing the same thing on the 0.2.1 system does not suffer with the same problem!! This is also true for the windows based platform where all the dev work is done.
I have introduced cleanDeadPool() to the destruction of these "dynamic" windows, but it doesn't seem to free up the memory. I have a large number of text boxes showing "results" of the game running, and these require a huge amount of RAM. - when the game resumes after they have been destroyed - there is insufficient RAM to continue running.
I am working through the system code now to see if there is anything else - but there are certainly the above issues with the system.
Any thoughts anyone?
Cheers
I must admit, my biggest dialog has "only" about 20-30 items it loads the same time. In debug mode it takes a few (3-4) seconds to load, in release, it loads instantly.