Like. Seriously. In the history of me playing this game (for about 2300 hours) the game never needed more than 800 MB. Now that's tripled, probably since the last update (which also brought back the "can't load lump x, allocation of xxxxxxxx bytes failed!" error which causes the game to crash after every map change).
Something somewhere is leaking memory into the main memory pool, and every time a map loads (which is a single big file) the game doesn't know where to put the map into the memory so it just crashes.
Now before people go "u have toaster rite?": no I don't have a toaster. i7-4870HQ, 16GB of DDR3-1600 RAM, GT750M with 2 GB dedicated GDDR5 RAM, some PCI-e SSD. Only difference is I run OS X 10.10.3. Now this all started occurring after the April 29th update, before that it was fine.
Is there any way to get TF2 back to normal memory usage via console commands/launch options or do I have to wait until Valve decides to fix this? Valve should be aware of this, I've sent them at least 8 or 9 crash reports in the last 2 days. Now we wait.
Something somewhere is leaking memory into the main memory pool, and every time a map loads (which is a single big file) the game doesn't know where to put the map into the memory so it just crashes.
Now before people go "u have toaster rite?": no I don't have a toaster. i7-4870HQ, 16GB of DDR3-1600 RAM, GT750M with 2 GB dedicated GDDR5 RAM, some PCI-e SSD. Only difference is I run OS X 10.10.3. Now this all started occurring after the April 29th update, before that it was fine.
Is there any way to get TF2 back to normal memory usage via console commands/launch options or do I have to wait until Valve decides to fix this? Valve should be aware of this, I've sent them at least 8 or 9 crash reports in the last 2 days. Now we wait.