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/18/06 5:46 p.m.
In Response To: Re: Massive memory leak in Forge using Classic (Johannes Gunnar)

I just fired up Forge 1.0.4 with M1 Map file and I don't get any of the above mentioned problems in OS 10.3.9 with Classic running 9.1. Forge has the standard 7MB of RAM allocated. The machine has 1.5GBs of RAM. I guess what I'm getting at is twofold:
- something's up with the specific Map files that you are opening in Forge
- something's up with your Classic environment. I don't really know if you have the option of hooking up another drive (through firewire) that has OS 9 on it, but if you do..it'd be interesting to set up your Classic System Preferences to start up that OS 9 as Classic and not your default installation and to see if you're getting the same problem (you can pick what OS 9 should be "Classic" in that System Preference)...at least that way you'd know if it's the Classic you have, OS X, or your map files.

[ 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:
: I just fired up Forge 1.0.4 with M1 Map file and I don't get any of the : above mentioned problems in OS 10.3.9 with Classic running 9.1. Forge has : the standard 7MB of RAM allocated. The machine has 1.5GBs of RAM. I guess : what I'm getting at is twofold: - something's up with the specific Map : files that you are opening in Forge : - something's up with your Classic environment. I don't really know if you : have the option of hooking up another drive (through firewire) that has OS : 9 on it, but if you do..it'd be interesting to set up your Classic System : Preferences to start up that OS 9 as Classic and not your default : installation and to see if you're getting the same problem (you can pick : what OS 9 should be "Classic" in that System Preference)...at : least that way you'd know if it's the Classic you have, OS X, or your map : files. :

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/18/06 5:46 p.m.
	In Response To: Re: Massive memory leak in Forge using Classic (Johannes Gunnar) I just fired up Forge 1.0.4 with M1 Map file and I don't get any of the above mentioned problems in OS 10.3.9 with Classic running 9.1. Forge has the standard 7MB of RAM allocated. The machine has 1.5GBs of RAM. I guess what I'm getting at is twofold: - something's up with the specific Map files that you are opening in Forge - something's up with your Classic environment. I don't really know if you have the option of hooking up another drive (through firewire) that has OS 9 on it, but if you do..it'd be interesting to set up your Classic System Preferences to start up that OS 9 as Classic and not your default installation and to see if you're getting the same problem (you can pick what OS 9 should be "Classic" in that System Preference)...at least that way you'd know if it's the Classic you have, OS X, or your map files.

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: : I just fired up Forge 1.0.4 with M1 Map file and I don't get any of the : above mentioned problems in OS 10.3.9 with Classic running 9.1. Forge has : the standard 7MB of RAM allocated. The machine has 1.5GBs of RAM. I guess : what I'm getting at is twofold: - something's up with the specific Map : files that you are opening in Forge : - something's up with your Classic environment. I don't really know if you : have the option of hooking up another drive (through firewire) that has OS : 9 on it, but if you do..it'd be interesting to set up your Classic System : Preferences to start up that OS 9 as Classic and not your default : installation and to see if you're getting the same problem (you can pick : what OS 9 should be "Classic" in that System Preference)...at : least that way you'd know if it's the Classic you have, OS X, or your map : files. :
	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: