Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Lua error (memory) - not enough memory #508

Open
kamlanaut opened this issue Apr 27, 2014 · 13 comments
Open

Lua error (memory) - not enough memory #508

kamlanaut opened this issue Apr 27, 2014 · 13 comments

Comments

@kamlanaut
Copy link

I have been encoutering this problem, everytime when I warp or zone into an area I get a 5-10 second freez, then everything start running normally again, then this message would show up.

these are the plugin i'm using:
chars
distance
dynamishelper
highlight
silence
update

@Byrth
Copy link
Contributor

Byrth commented Apr 27, 2014

What is the "update" addon?

@z16
Copy link
Member

z16 commented Apr 27, 2014

It's an addon that allows updating Windower by typing //update or alternatively enable periodic update checks by specifying an interval.

@Byrth
Copy link
Contributor

Byrth commented Apr 27, 2014

Well, if it's known then my only suspect is dynamishelper, really.

For @kamlanaut - Arcon and I are discussing which addon might be causing this. The error that you are getting is often caused by infinite recursion (a loop that cannot be exited) where something is added to memory with each loop. Because it's slowly increasing memory, eventually it hits the maximum for LuaCore and LuaCore terminates it and thus forces it to exit the loop. If it wasn't adding anything to memory, it would just freeze your process indefinitely.

@z16
Copy link
Member

z16 commented Apr 27, 2014

Can you unload everything and see if it works, then try to enable them one by one to see if it's an addon causing it?

@z16 z16 closed this as completed Apr 27, 2014
@z16 z16 reopened this Apr 27, 2014
@z16
Copy link
Member

z16 commented Apr 27, 2014

Closed by accident...

@smd111
Copy link

smd111 commented Apr 28, 2014

wouldn't this command let you know what addon is causing the memory over-run
//lua memory
you would just have to use it a few times and see which one is gaining size

@z16
Copy link
Member

z16 commented Apr 28, 2014

But if it only happens on zoning, it would be hard to time it exactly right, as when the memory overruns, the function stops executing and the garbage collector would clean it up again.

@z16
Copy link
Member

z16 commented May 6, 2014

Apparently this is due to Highlight. I'll look into it.

@Byrth
Copy link
Contributor

Byrth commented Jul 19, 2014

This may be fixed on -dev. I'm going to start using highlight and see if I can reproduce the issue. If not, I'll close it in a week or so.

@Byrth
Copy link
Contributor

Byrth commented Jul 27, 2014

I haven't been able to reproduce this, so I assume it is fixed.

@Byrth Byrth closed this as completed Jul 27, 2014
@IBHalliwell
Copy link

Hello,

I just had this issue with Highlight today (5/6/2016) and my Son had it yesterday (5/5/2016).

Thank you.

@Byrth Byrth reopened this May 8, 2016
@angelskiss11
Copy link

I have been having this issue ongoing as well. June13, 2016. I just turned off Highlight to see if it resolves the issue.

@Imoq
Copy link

Imoq commented Sep 6, 2023

2023, this is happening to me. Not sure how to reproduce it, it only happens in Dynamis W3 it seems. I've just unloaded the Highlight plugin for now and will see on next run if my freezes continue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants