Re: Massive memory leak in Forge using Classic


	/-/S'pht-Translator-Active/-/

Re: Massive memory leak in Forge using Classic

Posted By: Tycho Date: 3/17/06 7:26 p.m.
In Response To: Re: Massive memory leak in Forge using Classic (Johannes Gunnar)

: the main thing is that this has never acted like this before.
: the only thing that i've changed on my comp is a 256mb RAM upgrade (now 512mb
: RAM) but i would think that would have the opposite effect :P
Unless it's bad RAM, which could cause the effect you described. Also, it could be a corrupt extension in the Classic environment, like a QuickTime extension or OpenGL or who knows what. That Classic system preferences does allow you to control what extensions load (by opening the Extensions Manager at Classic startup) or turning them all off. The same system preferences also give you memory information of the classic programs running if you're using 10.3 or 10.4. Last but not least, Classic applications do allow you to specify in their Get Info dialog box how much RAM they should use...if you're concerned that Forge uses too much, give it a generous, but limited RAM allocation and see if Classic ends up using a lot more than that. Good luck. :)

[ Post a Reply | Message Index | Read Prev Msg | Read Next Msg ]
Pre-2004 Posts

Replies:

[ Post a Reply | Message Index | Read Prev Msg | Read Next Msg ]
Pre-2004 Posts

Your Name:
Your E-Mail Address:
Subject:
Message:
: Unless it's bad RAM, which could cause the effect you described. Also, it : could be a corrupt extension in the Classic environment, like a QuickTime : extension or OpenGL or who knows what. That Classic system preferences : does allow you to control what extensions load (by opening the Extensions : Manager at Classic startup) or turning them all off. The same system : preferences also give you memory information of the classic programs : running if you're using 10.3 or 10.4. Last but not least, Classic : applications do allow you to specify in their Get Info dialog box how much : RAM they should use...if you're concerned that Forge uses too much, give : it a generous, but limited RAM allocation and see if Classic ends up using : a lot more than that. Good luck. :) :

If you'd like to include a link to another page with your message,
please provide both the URL address and the title of the page:
Optional Link URL:
Optional Link Title:

If necessary, enter your password below:
Password:

Problems? Suggestions? Comments? Email maintainer@bungie.org
Marathon's Story Forum is maintained with WebBBS 5.12.

	Re: Massive memory leak in Forge using Classic
	Posted By: Tycho	Date: 3/17/06 7:26 p.m.
	In Response To: Re: Massive memory leak in Forge using Classic (Johannes Gunnar) : the main thing is that this has never acted like this before. : the only thing that i've changed on my comp is a 256mb RAM upgrade (now 512mb : RAM) but i would think that would have the opposite effect :P Unless it's bad RAM, which could cause the effect you described. Also, it could be a corrupt extension in the Classic environment, like a QuickTime extension or OpenGL or who knows what. That Classic system preferences does allow you to control what extensions load (by opening the Extensions Manager at Classic startup) or turning them all off. The same system preferences also give you memory information of the classic programs running if you're using 10.3 or 10.4. Last but not least, Classic applications do allow you to specify in their Get Info dialog box how much RAM they should use...if you're concerned that Forge uses too much, give it a generous, but limited RAM allocation and see if Classic ends up using a lot more than that. Good luck. :)

Massive memory leak in Forge using Classic	Johannes Gunnar	3/17/06 5:22 a.m.
Re: Massive memory leak in Forge using Classic	Andrew Nagy	3/17/06 6:01 a.m.
Re: Massive memory leak in Forge using Classic	Johannes Gunnar	3/17/06 8:03 a.m.
Re: Massive memory leak in Forge using Classic	LegacyTyphoon	3/17/06 9:43 a.m.
Re: Massive memory leak in Forge using Classic	Johannes Gunnar	3/17/06 4:01 p.m.
Re: Massive memory leak in Forge using Classic	Andrew Nagy	3/17/06 5:34 p.m.
Re: Massive memory leak in Forge using Classic	Tycho	3/17/06 7:26 p.m.
Re: Massive memory leak in Forge using Classic	Johannes Gunnar	3/18/06 3:47 a.m.
Maybe Classic just doesn't like Forge	ukimalefu	3/18/06 5:35 p.m.
Re: Maybe Classic just doesn't like Forge	C Lund	3/18/06 11:56 p.m.
Re: Maybe Classic just doesn't like Forge	RyokoTK	3/19/06 3:22 a.m.
Re: Massive memory leak in Forge using Classic	Tycho	3/18/06 5:46 p.m.
Re: Massive memory leak in Forge using Classic	Aaron Sikes	8/2/06 6:18 a.m.
Re: Massive memory leak in Forge using Classic	treellama	8/2/06 8:46 a.m.
Re: Massive memory leak in Forge using Classic	Aaron Sikes	8/3/06 7:12 a.m.
Pfhorge v. Forge	thermoplyae	8/3/06 9:47 a.m.
Re: Pfhorge v. Forge	treellama	8/3/06 10:46 a.m.
Re: Massive memory leak in Forge using Classic	Philtron	12/19/12 9:10 a.m.



	Your Name:
	Your E-Mail Address:
	Subject:
	Message: : Unless it's bad RAM, which could cause the effect you described. Also, it : could be a corrupt extension in the Classic environment, like a QuickTime : extension or OpenGL or who knows what. That Classic system preferences : does allow you to control what extensions load (by opening the Extensions : Manager at Classic startup) or turning them all off. The same system : preferences also give you memory information of the classic programs : running if you're using 10.3 or 10.4. Last but not least, Classic : applications do allow you to specify in their Get Info dialog box how much : RAM they should use...if you're concerned that Forge uses too much, give : it a generous, but limited RAM allocation and see if Classic ends up using : a lot more than that. Good luck. :) :
	If you'd like to include a link to another page with your message, please provide both the URL address and the title of the page:
	Optional Link URL:
	Optional Link Title:
	If necessary, enter your password below:
	Password: