Console addon memory

ellmarie · June 21

Is there a fix to this? I keep getting the error 70 mg out of 100 mg memory then all my addons get disabled. I've deleted just about all I can. I don't have very many really. Mini map, harvest map, price fetcher and lazy crafter. Is there something else I need to be doing to clear some space?

PeacefulAnarchy · June 21

Not all addons use the same amount of memory. If it's anything like PC, Harvest map uses up a ton of memory.
I don't know what fixes are possible for you as I'm not on console.

Twohothardware · June 21

Try disabling just Price fetcher and see if you stop getting the memory error.

katanagirl1 · June 22

PeacefulAnarchy wrote: »

Not all addons use the same amount of memory. If it's anything like PC, Harvest map uses up a ton of memory.
I don't know what fixes are possible for you as I'm not on console.

I have HarvestMap, Murf’s Treasures, and Combat Alerts, and it’s not much memory at all, I’m going to say something like 40 mb for those but I think it said 250 mb total allotment for me.

It does say that HarvestMap is out of date but there is no way to update it. It works.

Gabriel_H · June 22

katanagirl1 wrote: »

It does say that HarvestMap is out of date but there is no way to update it. It works.

"Out of Date" is simply because the information file (.addon) doesn't have the latest game version number. The API that actually runs the addon is unchanged.

DragonRacer · June 22

I ended up uninstalling Harvest Map on PS5. I was running into similar issues. Ever since I uninstalled that one, I have been fine with Mini Map (plus the Circular addition), Price Fetcher, Lazy Writ Crafter, plus several others I am running (Murf's Lorebooks, Murf's Treasures, Code's Combat Alerts, Crutch Alerts, Auto-Bind, Auto-Collect Tome Points, Battle Scrolls, and I think a few others).

I loved the Harvest Map, don't get me wrong, but it seemed to be my culprit. It and Adventurer's Toolkit just were destroying my add-on memory and my issues stopped after yeeting those two.

DenverRalphy · June 22

DragonRacer wrote: »

I ended up uninstalling Harvest Map on PS5. I was running into similar issues. Ever since I uninstalled that one, I have been fine with Mini Map (plus the Circular addition), Price Fetcher, Lazy Writ Crafter, plus several others I am running (Murf's Lorebooks, Murf's Treasures, Code's Combat Alerts, Crutch Alerts, Auto-Bind, Auto-Collect Tome Points, Battle Scrolls, and I think a few others).

I loved the Harvest Map, don't get me wrong, but it seemed to be my culprit. It and Adventurer's Toolkit just were destroying my add-on memory and my issues stopped after yeeting those two.

Harvestmap barely takes up much memory at all. TSC price checker is a memory consuming beast. I don't know what issues Harvest Map is giving you, but memory issues would be the last thing I'd guess.

msgeek · June 22

wishlist:

a per-addon quota. e.g. 20mb. if more is used then only that addon gets disabled.
if most addons are tiny (2-4mb) then you'd be able to load way more than the naïve calculation of 100mb divided by 20mb would suggest.
that way everyone knows which addons are the true memory hogs.

LootAllTheStuff · June 22

I run Harvest Map, Can I Craft, Auto-Bind, and the NM activity one on XBSX with no problems. I suspect one of the other add-ons @DragonRacer is using may be the real culprit (memory leak?) but the additional requirement for Harvest Map pushed things too close to the edge.

DragonRacer · June 22

I'm not the OP having issues. Just added my anecdotal personal experience since a few of the add-ons OP uses align with ones I use, and I was sharing which one(s) I removed that cleared up the issues I had many, many months ago in the past.

code65536 · June 22

PeacefulAnarchy wrote: »

Not all addons use the same amount of memory.

Yes!

There are small trivial addons that consumes less than 0.1MB of memory. And there are behemoths that can consume over 40MB. And everything in between.

Unfortunately, because of the architecture underlying how addons work, there is no way to separate the memory usage of individual addons. (Also, such a separation between addons would add a lot of extra complexity and overhead and also act as barriers that restrict the versatility of what addons can do, and would ultimately be a case of a "remedy being worse than the malady".)

That means there's no "easy" way to determine how much each addon consumes and no way to establish quotas as someone else suggested.

But, it is possible to determine "the hard way" how much each addon consumes, by using a memory monitor and seeing what memory consumption looks like as you enable and disable individual addons.

I highly recommend Movable Addon Memory by M0R. This is a very simple addon with almost zero footprint of its own, and it was created specifically to help console users identify addons that use problematic amounts of memory.

spartaxoxo · June 23

I keep running into the same issue. I'm guessing it's Lib Async, which is used by both TSC and Mini Map? Or maybe I can only run one of these given I also have other add-ons? Should I reinstall them, would that help? Is this just too many?

code65536 · June 23

spartaxoxo wrote: »

I keep running into the same issue. I'm guessing it's Lib Async, which is used by both TSC and Mini Map? Or maybe I can only run one of these given I also have other add-ons? Should I reinstall them, would that help? Is this just too many?

This is unrelated to this thread, since this isn't an issue with console console memory usage.

This is a problem with the other console limitation: addon CPU usage.

Specifically, addons must yield control back to the game at least once every second (1000ms). If addons are processing a large amount of data and it takes them more than 1s, then you'll get this error. Like the memory limit, this is applied to every addon combined, so if addon A takes 600ms to process stuff and addon B takes 600ms to process stuff, then even though they each fall under the 1000ms limit, they will, together, trigger this error.

So if an addon needs to process a lot of data, then it needs to break that work down into smaller chunks and yield back control after every chunk, and LibAsync is something to help addons do this break-up-work-into-smaller-pieces thing. So in this case, the problem isn't LibAsync, it's with an addon that's using LibAsync.

Ah, but if LibAsync is supposed to help addons avoid this error, then why are you seeing it? Because LibAsync is not magic. It requires that the addon use it properly. If an addon needs to do 4000ms worth or work, breaking that down into 3 chunks will not be enough. Breaking it down into 5 chunks of 800ms is also a bad idea--it's cutting it too close and if there are other addons that are also doing this, then you'll blow past the 1000ms limit easily. Its work needs to be broken down into 20 or more pieces. So if you're seeing this error, then it means that an addon is at least trying to do the right thing, but they're still trying to do too much at once and need to divide up their work even more.

In any case, my guess is that in your case TSC is the culprit, because this is an issue that I know they've struggled with before.

spartaxoxo · June 23

code65536 wrote: »

spartaxoxo wrote: »

I keep running into the same issue. I'm guessing it's Lib Async, which is used by both TSC and Mini Map? Or maybe I can only run one of these given I also have other add-ons? Should I reinstall them, would that help? Is this just too many?

This is unrelated to this thread, since this isn't an issue with console console memory usage.

This is a problem with the other console limitation: addon CPU usage.

Specifically, addons must yield control back to the game at least once every second (1000ms). If addons are processing a large amount of data and it takes them more than 1s, then you'll get this error. Like the memory limit, this is applied to every addon combined, so if addon A takes 600ms to process stuff and addon B takes 600ms to process stuff, then even though they each fall under the 1000ms limit, they will, together, trigger this error.

So if an addon needs to process a lot of data, then it needs to break that work down into smaller chunks and yield back control after every chunk, and LibAsync is something to help addons do this break-up-work-into-smaller-pieces thing. So in this case, the problem isn't LibAsync, it's with an addon that's using LibAsync.

Ah, but if LibAsync is supposed to help addons avoid this error, then why are you seeing it? Because LibAsync is not magic. It requires that the addon use it properly. If an addon needs to do 4000ms worth or work, breaking that down into 3 chunks will not be enough. Breaking it down into 5 chunks of 800ms is also a bad idea--it's cutting it too close and if there are other addons that are also doing this, then you'll blow past the 1000ms limit easily. Its work needs to be broken down into 20 or more pieces. So if you're seeing this error, then it means that an addon is at least trying to do the right thing, but they're still trying to do too much at once and need to divide up their work even more.

In any case, my guess is that in your case TSC is the culprit, because this is an issue that I know they've struggled with before.

Thank you for the detailed reply! I really appreciate it. Would disabling that add-on unless I'm trying to actually list something help in the meantime?

code65536 · June 23

spartaxoxo wrote: »

Thank you for the detailed reply! I really appreciate it. Would disabling that add-on unless I'm trying to actually list something help in the meantime?

Yes. Because pricing data for tens of thousands of items is inherently and unavoidably heavy, I know that a number of console users do exactly that: enable it only when they need to use it.

spartaxoxo · June 23

code65536 wrote: »

spartaxoxo wrote: »

Thank you for the detailed reply! I really appreciate it. Would disabling that add-on unless I'm trying to actually list something help in the meantime?

Yes. Because pricing data for tens of thousands of items is inherently and unavoidably heavy, I know that a number of console users do exactly that: enable it only when they need to use it.

Thank you! I'll make sure to do that then since I don't always have stuff to sell. Appreciate the help

katanagirl1 · June 23

I should note that for HarvestMap I only show nodes in the overland and not on compass or the zone map. It’s all I need and I feel that it probably puts the lightest load on my machine to do the job. I also turned off stolen containers just because it clutters up the display too much for me.

I don’t use pricing addons and just hit the capital traders to search for items to get a feel for the price I should set, just like I always did.

Fennorian · June 24

They need to fix this bc atp it’s pay to play on Xbox with the whole pc app bs with 300 fps uncapped playing on Xbox servers cuz the memory on console itself is awful 🙃

M0R_Gaming · June 24

Fennorian wrote: »

They need to fix this bc atp it’s pay to play on Xbox with the whole pc app bs with 300 fps uncapped playing on Xbox servers cuz the memory on console itself is awful 🙃

What does FPS have to do with UI memory? If we are talking like ddr4 vs ddr5 ya I guess we could see a difference, but that is unrelated to Addons entirely - that will just improve overall game performance because the game will be able to load assets faster.

I do think the 100mb RAM limit is a bit low, but that limitation is forced by Xbox and PlayStation themselves, requiring precise budgeting of memory.