Thread Back to Bugs Truespace Archive Announcements Archive: Tech Forum Bugs Business Collaboration Feature suggestions Game Development Hardware Image Gallery Interactive Artwork iSpace Monthly Modeling Contest New Users Rants and Raves Roundtable Scriptorium Speed Model Challenge Tech Forum The Garage truePlay Visitor Area Work in Progress Site Features Citizens List Badges & Achievements Events Directory News and Articles Worlds List About Alphaworld Search Object Paths Activeworlds Support Download Activeworlds Quickstart Tutorial Historic Archives Truespace Archives Newsgroup Archives

Saving to Library problem About Truespace Archives These pages are a copy of the official truespace forums prior to their removal somewhere around 2011. They are retained here for archive purposes only. Saving to Library problem // Bugs 1  |   Order by default Post by weaveribm // Aug 19, 2007, 12:12pm weaveribm Total Posts: 592 Across two operating systems and TS7.51 installations and reinstallations on my system I am getting a crash with all system RAM grabbed by TS7.51 I work around this by: Saving to a Library (Insert) and waiting until system RAM is nearly full at around 1.6GB in use by TS7.51, then if TS settles down and the save was ok I start a New Scene and load back in the scene I just saved. Then I can work as normal with TS7.51 running normally in ~500MB system RAM until the next scary save when exactly the same thing happens. It's making me edgy. Please find the crash dump attached. Please communicate with your loyal TrueSpace user Caligari Support and let me know if either there is a fix on the way or you need more information. Please work hard at not ignoring your loyal customers? Passionately loyal customers. Right now. I have tried to be reasonable and not to complain too much but I do feel that I am being ignored as I reported this problem a while back with the crash dump and a what-happened report and I have heard absolutely nothing in return for my disciplined and sensitive approach. If this problem is something to do with my system then please have the common courtesy to tell me one way or another Caligari Support? Thanks. Peter Post by weaveribm // Aug 20, 2007, 3:05am weaveribm Total Posts: 592 I have more information to report to Tumbleweed Central :) Back at work today I brought the scene into my Research Machines er, machine which has a maximum system memory for the model of 512MB The RM machine is only 900MHz but working on the (39MB) scene was fine This time on saving to a Library and observing pagefile use from Task Manager I saw more than 1.37GB gradually filling up as the machine offloaded whatever work it needs to be doing After lunch :) I had to reboot (not surprisingly) but this operation tells me that I need to find out why my pagefile on my home machine is not cooperating with TS7.51 I have a large pagefile set up at home (common on gaming machines) so there I will switch back to allowing XP to handle the system pagefile and report back. I did have some problem with the pagefile (under TS only) already, and I did not see the pagefile expanding - as it should - on my home machine. This must be a clue. Generally very pleased with TS7.51's economy and Workspace has no problem at all saving the same scene. Someone at Caligari is planning very large scenes perhaps. Four million avatars turning up on Thursdays :) Bridge on or off doesn't affect this saving problem I think but I ought to be sure to turn off the bridge before saving to a Workspace Library to test Peter Post by weaveribm // Aug 20, 2007, 10:53am weaveribm Total Posts: 592 Now we're getting somewhere :) Same with Windows managing the pagefile That leaves the scene. Repeat DeleteOneObject SaveSceneToTheLibrary If SavingNowWorksOk Then NormalServicesAreResumed If AllObjectsDeleted Then StartPullingHairOut(MassPanic,BiteFurniture) Until NormalServicesAreResumed BlissRestored=True That should do it :) It's lucky they pay me for solving problems. My employers I mean :) Peter Post by weaveribm // Aug 20, 2007, 10:59am weaveribm Total Posts: 592 No wait even better, try the binary search for the offending object/texture. Use your enemy's weapon against him "Yes HAL you'll find you can do that..." :) Delete 50% of the objects in the scene. If all is well again the offender is in the first 50% deleted objects And so on. Surprised you didn't think of that :) "But there are only three objects in the scene" :) Peter Post by weaveribm // Aug 21, 2007, 9:49am weaveribm Total Posts: 592 Turns out the perpetrator was in the first half, sorted and back to lightning saves to Library and a steady 400MB phew :) Thank goodness for that it was a very complex object that simply needed to have the MeshCollapse plugin run over it on Modelside, no hint of TrueSpace bugginess. Let that be a lesson to you. Me I mean. I'm only saying what you're thinking gentle reader :) Thanks to many experienced TS people again who've been advising on the economy of collapsing hierarchies and generally not being an idiot! We're getting there I promise :) Peter Post by Jack Edwards // Aug 21, 2007, 11:23am Jack Edwards Total Posts: 4062 Peter, if you still have the object that causes the memory leak I'm sure the devs would be very happy to see that.... ;) -Jack. Post by weaveribm // Aug 21, 2007, 2:53pm weaveribm Total Posts: 592 Thanks Jack, quite right - I've submitted a report :) Peter

Awportals.com is a privately held community resource website dedicated to Active Worlds.
Copyright (c) Mark Randall 2006 - 2024. All Rights Reserved.