# Space Rocks 3D! **URL:** \ **Category:** Show & Tell\ **Tags:** featured-game, game\ **Created:** [February 24, 2021, 3:59pm UTC](https://forum.makecode.com/t/space-rocks-3d/6334 "2021-02-24T15:59:47Z")\ **Posts on this page:** 1\ **Showing post:** 21
**Author:** ![kwx](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.makecode.com/kwx/32/1545_2.png) [@kwx](https://forum.makecode.com/u/kwx)\ **Post date:** [February 24, 2021, 10:57pm UTC](https://forum.makecode.com/t/space-rocks-3d/6334/21 "2021-02-24T22:57:07Z")
> [@2ndClemens](#): > > Works well on the Meowbit till level 4 where it gets quite slow. Crashes at level 5. It’s a bit hard to find specifications, but it appears that the Meowbit has 96kB RAM, compared to 192kB RAM on the PyGamer? I suspect that it’s running out of memory and struggling with garbage collection to make room. While I have tried to reuse data structures across frames, the program still doing a fair amount of on-the-fly allocation of small arrays. Are there good resources to help investigate memory usage? I found the [Memory Tools in MakeCode Arcade](https://forum.makecode.com/t/memory-tools-in-makecode-arcade/499) thread, but my brief experiments with trying to get console output from the PyGamer had been unsuccessful. [Profiling memory](https://makecode.com/js/profiling#profiling-memory) says that the heap snapshot doesn’t track strings or numbers, and much of the program’s data is numbers… @ggiscool, I like your dashboard, but I worry that adding a fullscreen image (~10kB each) may make it even harder for this to fit on hardware. --- _[View the full topic](https://forum.makecode.com/t/space-rocks-3d/6334)._