Wiktionary talk:Lua memory errors

Potential Solutions for The Memory Error
Hmm, this is going to be a hard one to figure out on the fly like this, especially given that I have not seen the website's source code, but here is a potential solution for your problem.

I guess algorithmically so, you could restructure the Wiki API to functionally close expanded modules after you read them, providing the illusion that the module is still there, but effectively none of its contents are being called into memory from your servers. This is not satisfactory, for example, if you wanted to have multiple wiktionary pages open, to cross reference the closed module sections and to also view other pertinent modules that can't be loaded into memory.

Also, instead of loading every module at once, have the modules not display data which must be called upon first by opening the modules, wherein this should only be applied on the particularly troublesome pages.

I prefer the first solution more, because it can be particularly annoying to have open and close modules at will.

This can be done without having to constantly refresh the website and it's a good way of partitioning and allocating memory.

A good case example of what would happen is that if you tried to hit that memory cap, you would, per the next module you go to, encounter such errors wherein the proper characters and symbols cannot be displayed. A solution for this would be to, once again, manually reopen this module after other modules are closed.

Sincerely, John.

Edit: I apologize, I was getting the idea of modules confused with what are submodules in the form of page sections. I am explicitly talking about page sections in the original solution that I provided, but not necessarily modules verbatim.

Increase memory limit?
Is there any way to increase the memory limit? Everything else doesn't seem like a good solution. Several popular pages are basically unusable because of these memory errors. Tajoshu (talk) 19:51, 27 June 2023 (UTC)