Loading Profile...
Why is the latest vivaty player a resource hog?
I have been using flux for development and just tried the new vivaty player. When I open up my 3D model and explore the scene etc, the appliciation keeps requesting more and more RAM. It will use up all physical RAM and then use all of my virtual RAM until the computer comes to a halt from a lack of resources. This does not happen with the old flux player.
I am running this on a Pentium 4 with 1GB of Ram and 2GB virtual memory under Windows XP SP3.
I am running this on a Pentium 4 with 1GB of Ram and 2GB virtual memory under Windows XP SP3.
1
person has this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?The increased RAM use can be caused by either the player or the 3D model, or both. Have you made changes to your 3D model between the old and new player? Do you see the increased RAM use viewing other 3D models?
We'll continue to investigate on our end.2 Comments
Add a comment
This answers the question
-
I have not made any changes to the model. As a matter of fact, I can run the same model in both the older flux player and the new vivaty player simultaneously. I have a webpage with the active control object on it. I then can use a browser to load the page with the new or old player. The browser with vivaty greatly increases its ram usage while manipulating the model whereas the flux player does not. With only a few minutes of manipulating the model, the RAM usage which may have started around 50MB will exceed 1GB. This problem occurs with all of my models.. -
In all of my models, I have a proximity sensor around the whole world. Inside the world I have an object, say a vehicle. I have a 2d layer which reports the current position from the proximity sensor. The proximity sensor position_changed parameter is routed to a script function which updates the 2d layer to report the location. The issue as it turns out is that the script function called by the proximity sensors sets my string to a "new MFString". These calls seem to keep allocating memory but not deleting it. As a result, the memory usage continues to increase. Every time the model moves, the position will change a new MFString is allocated. The same problem occurs with "new String".
