← Return to game
Log in with itch.io to leave a comment.
perfect 100% 10/10
Thanks!
Finished it in an hour: Great game 👍Possible improvements: - Minimize panels to reduce necessary animation renders
Glad you enjoyed it!
That's a good idea about minimizing.
Another great LSDJAM game.
This event is really bringing out the best in you guys.
Kudos <3
im in frkn love with this, please expand it more, im 100% into this game ;-;
Thank you very much!I don't actually have plans to work more on this I'm sorry but it might happen in the future :)
i love it but why does it fill up my ram so fas
I think it's either the synthesizer or maybe the defrag, as the process of defragging is low-key actually executed.
Glad you enjoyed it :)
Ah, you might be able to help some of the leaking by reusing the defrag data rather than generating new one and hoping the browser GC gets around to it (you might be holding a reference somewhere and blocking the cleanup, it's pretty easy to do)
The single defrag blocks that get organized are always the same and get reshuffled, so I'm not sure what I could improve there.
Then they're probably not the ones that are causing the memory leaks, then :P
I don't really know what tools are easily available for traiging the leaks, aside from built in browser ones, unfortunately!
good
Thanks ^^
wow omg
← Return to game
Comments
Log in with itch.io to leave a comment.
perfect 100% 10/10
Thanks!
Finished it in an hour: Great game 👍
Possible improvements:
- Minimize panels to reduce necessary animation renders
Glad you enjoyed it!
That's a good idea about minimizing.
Another great LSDJAM game.
This event is really bringing out the best in you guys.
Kudos <3
Thanks!
im in frkn love with this, please expand it more, im 100% into this game ;-;
Thank you very much!
I don't actually have plans to work more on this I'm sorry but it might happen in the future :)
i love it but why does it fill up my ram so fas
I think it's either the synthesizer or maybe the defrag, as the process of defragging is low-key actually executed.
Glad you enjoyed it :)
Ah, you might be able to help some of the leaking by reusing the defrag data rather than generating new one and hoping the browser GC gets around to it (you might be holding a reference somewhere and blocking the cleanup, it's pretty easy to do)
The single defrag blocks that get organized are always the same and get reshuffled, so I'm not sure what I could improve there.
Then they're probably not the ones that are causing the memory leaks, then :P
I don't really know what tools are easily available for traiging the leaks, aside from built in browser ones, unfortunately!
good
Thanks ^^
wow omg