Well, allocation is what triggers GC and there appears to be a fair amount of that in your program. I am not in a good position to run your code and nothing jumps out at me from a first glance at the gist but probably it is allocation that originates there (not that that means your code is necc. buggy).
Fundamentally, functional image construction (and lists) requires allocation and allocation requires GC. That said there is probably something's we can fix here. I will try to take a closer look in the coming days of no one beats me to it. Robby On Wednesday, August 7, 2013, Jack Firth wrote: > Hey users, I'm experimenting with some simple games using big-bang from > 2htdp/universe and I keep running into stuttering problems. It seems to be > the garbage collector slowing things down (green recycle symbol in drracket > is on whenever the program is frozen). > > Increasing the memory limit or removing the limit altogether doesn't seem > to affect the problem, and I've checked in the IRC and it occurs on other > machines as well, all of which have the specs that it shouldn't have any > problems with slowdown. Are there issues with big-bang and it's event > handling? > > Source - https://gist.github.com/Universalist235/6171371 >
____________________ Racket Users list: http://lists.racket-lang.org/users
