For anyone who's been following this channel for a bit, I've mentioned that this game leaks memory but we couldn't figure out how or why the game does this. Just last week I've pinpointed what causes the game to leak memory. If you were to somehow go OoBs and unload the map, the game leaks memory each time you unload the map via OoBs. My guess is that the game doesn't know how to properly clean up objects when unloading maps this way and the game orphans these objects in memory. So far I've managed to get some textures and particles to unload from messing around with this but I can't single handily figure out every single possible skip you can do with this. For anyone that's interested in glitch hunting this game, this is a huge discovery that should be messed around with.

Since the last post I've made on the Discord server I've found several things that I didn't know about a few months prior. Some things that I've found with this method of leaking memory since then are:
-This method of memory leaking works on all versions of the game.
-This method works on both the GC and Wii with little to no differences on how many times you can unload/load a map before crashing the console.
-Can confirm that you can unload certain triggers in Thorntail Hollow such as the Egg Minigame trigger not loading but I haven't found a way to do this consistently.
-This method works in Thorntail Hollow and Lightfoot Village
-I wasn't able to get the game to crash when doing this at Snowhorn Waste. I know that I wasn't memory leaking in that area since I've unloaded and loaded the area about 100 times with nothing getting affected by this method there. However, this doesn't mean that it's not possible to memory leak at Snowhorn Waste since I was only able to test this method out in only two areas of the Waste.

Things that still need to be looked at:
-Find out what is being orphaned. This can help eliminate some places to test this out if it's a specific prop/props that are being orphaned when doing this.
-Find out if we can overwrite key memory addresses of props and/or cutscenes with junk data with this method.

We've narrowed down what causes the memory leak at Thorntail Hollow to be the WarpStone which makes this memory leak only exclusive in some places in Thorntail Hollow where the WarpStone is loaded in. However, I still think there's some other objects that are causing a memory leak in Thorntail Hollow since doing this method at different locations and at different points of the game require a different amount of zoom-ins before crashing. Also we can confirm that objects from other maps can get unloaded from this memory leak at Thorntail Hollow as seen in this video below.

I must mention that in order to unload objects in other maps you'd have to save at the map which you want to unload certain objects then go to Thorntail Hollow and perform the memory leak.

I should have posted these when I first made this post, but the codes below are to enable the debug menu for this game if anyone else is interested on trying to figure out what causes this memory leak. You'd also need to have enabled the debug text cheat which. If you don't know how to do this, read through this section here https://tcrf.net/Star_Fox_Adventures#Development_Stuff

Gecko Code (Only works for 1.0)
c6148b78 80137948
c62510cc 80137948
c6246e04 80137948
c61378a8 80137948
c213798c 0000000d
91410024 7d6802a6
91610068 3c60803e
8063bc14 80810008
80a1000c 80c10010
80e10014 81010018
8121001c 81410020
81610024 3c008028
6000f688 7c0803a6
4e800021 3c80803e
80a4bc14 7ca51a14
38a50001 90a4bc14
80a10068 7ca803a6
60000000 00000000

Adding c6148bc8 80137948 will give additional Tricky debug text (I doubt he's causing the memory leak).

Adding c607d6dc 80137948 will display all OSReport messages.

Adding 003dcded 00000001 will give you map cords.

Action Replay (Only works for 1.0)
04137948 4BF45D94
04148B78 4BF34B64
04148BC8 4BF34B14
042510CC 4BE2C610
04246E04 4BE368D8
0428F7DC 4BDEDF00

Also it seems that the Warpstone doesn't have as much of a role in this memory leak than we first thought he had. The game uses about 75%-85% of memory in the areas where the memory leak occurs. I have no idea what is using this much memory in these locations but I'd say that this is the likely culprit to the memory leak than the Warpstone being the sole reason at this point.

Edit: Seems like the magic gem and the particle effects don't get freed up when Thorntail Hollow gets unloaded. This might be one of the major factors to the memory leak but I doubt it's the only thing since it still doesn't make sense that the amount of zoom-ins require before the game crashes changes based on your location and your game progress.

Image of the Warpstone area before it's unloaded:

Image of the Warpstone area when it's unloaded (Magic gem and it's effects are still loaded in behind Tricky's food counter)

Seems like there's a pattern with the memory leak, if there's an adjacent map that we can load from OoBs a memory leak will occur. There's another place where we can do this memory leak besides Thorntail Hollow and it's at the corner of Lightfoot Village closest to Cape Claw. Here's a picture that shows the positioning of all of the maps that this game has to give you an idea of where a memory leak can theoretically occur. Thanks to Rena for finding this out and for making this image:

Based off this picture, we can also theoretically leak at Cape Claw with Krazoa Palace and at Cloudrunner Fortress (Although there's no way to get OoB in these areas normally) but we haven't been able to leak at these areas yet.

As I've mentioned in my Discord post, this is probably one of, if not, the largest discovery for this game since ESW that can lead to huge changes for both Any% and possibly the 100% routes for this game. However, since this trick involves overwriting memory addresses, it'll probably take some time to find any use for this trick. It doesn't help that I also don't have as much free time to mess around with this glitch. If anyone is interested in glitch hunting for this game I'd still say that this glitch should be looked at.