mousestate = Mouse.GetState(Window); // with or without the window as a parameter.
The above line all alone generates about 1 megabyte of garbage every minute when i run with is timestep off.
Granted this is basically a empty project but im trying to eliminate garbage collection in tuning up my ui class to allow it to be a standalone project. This is vexing because i constantly see it dropping about 8kb like a hearbeat even when i run at 60 fps.
Does anyone know of a way to prevent it from creating garbage ? Or a alternate way to poll the mouse.
Ive been tracking garbage for month in my game and now you say it, there is garbage in the mouse. Getstate method.
At least in the mouse.windows.cs when doing a setposition call. A var and a new point is created each time it is called.
Have to go to work ill check the other methods later
So guys, this garbage is collected though, right? I mean… I feel like I would have noticed if my RAM use kept escalating, but I haven’t actually checked, and I DO have all those modern gigs of ram for garbage to pile up on.
Sure it may be unnoticeable, but calling GC takes some cycles and makes the app slowdown/hand/stutter in certain cases.
For instance, the mouse is not a big issue for me but as i set its position every frame to be at middle screen, it WILL create unwanted garbage.
I don’t have garbage with GetState though. A blank project with just this methods says nothing special about a memory leak
A variable is allocated on the stack. A Point is a struct, and again it is allocated on the stack. These do not allocate memory from the heap, and it is heap memory that is tracked by the garbage collector.
This is why it is important to declare which platform you are using. Mouse.GetState() in MonoGame.Framework.Windows does not generate garbage. Mouse.GetState() in MonoGame.Framework.DesktopGL does generate garbage.
This is why it is important to declare which platform you are using.
Mouse.GetState() in MonoGame.Framework.Windows does not generate
garbage. Mouse.GetState() in MonoGame.Framework.DesktopGL does generate
garbage.
Great arrg, Im using the cross platform one so ya basically the desktopGL on windows i guess, i should of said that…
Ya its creating garbage i add it and see it make garbage, remove it and it stops the real problem is i can’t get that garbage to stop being collected or reuse it.
Keyboard does it too when a key is actually pressed, but i haven’t isolated the call from my keyboard class to test that its not just my calls. I can live with garbage only when i press a key even if it is. The mouse is just doing it having that call in there which is constant.
So the dx version doesn’t generate garbage then ?
Seems odd that a call like this would generate garbage anyways unless somethings getting boxed that shouldn’t be.
Is there a work around other then switching to DX to prevent GetState on GL from creating garbage and collecting it ?
FYI the directX version also generates garbage. It’s the most garbage generated in my application right now, one can see the gc generate a lot when moving, it’s almost static when keeping still. Not explicitly getstate() though.
