Oh, i see, no i have 11.4.
I actually checked for version in the wiki first thing and the ... syntax is also listed there, i was unaware its not actually working.
Thanks.

I am trying to draw a circle directly to a canvas. Like canvas=love.graphics.newCanvas() canvas:renderTo(love.graphics.circle,"fill",9,9,9) The wiki states: Canvas:renderTo( func, ... ) is the syntax, assuming that means func is called with ... as its arguments. But regardless of what is w...

Its interesting that at doesnt crash at least.

Your understanding of a bug seems to be wildly different than mine.
Nothing of this has anything to do with lua or löve or how they work.
I piece of code, regardless of its language, that uses ram for no reason is buggy.
The type of bug is a memory leak.

Well, for me it doesn't. According to top , memory keeps growing until VIRT reaches 8,364,896 and RES reaches 7,397g, then VIRT it goes back to 8,340,316 and RES to 7,374g and then it stays in that loop. I have 32 GB in case that's important. So no, for me that's not a memory leak, it just imposes ...

I read that as "the man is not dead, he would be alive if his heart would be beating" Yea no shit, if you adjust GC its not a problem, but then you also dont use the same code. And the point is of this code having a problem, not the _fixed_ one. In other news, this crashes my computer and ...

Even if your entire program is just Font = love.graphics.newFont( 12) Font = love.graphics.newFont( 21) In my book thats a memory leak, those two lines cause a memory leak. Because it fits the definiton of "not freeing unused data". And thats the whole thing, this line, it fits so it is. N...

There is no fancy wording here. Take the first line from wikipedia "a memory leak is a type of resource leak that occurs when a computer program incorrectly manages memory allocations[1] in a way that memory which is no longer needed is not released." Which i read as a clear black and whit...

This is the very definition of a memory leak.
And of course its not anymore if you call garbage collect, i mean.... thats the point.
What are you trying to say here?

This is already cooler than 90% of what you find in comercial pool games for old consoles.

The problem here is that this kind of game is all about physics, you gotta have to nail it or else its garbage.
So pool is not the smartest starting point to get into game dev.

Practical example for a memory leak: Have a textbox, have it have a zoom in/out function. We reload our font with Font = love.graphics.newFont( zoom) _Font_ is overwriten each time so logically we would assume the old font data is discardet as it is no longer referenced. This is not the case because...