Finding the path of a loaded module

Looks like running it using 'racket' on the terminal instead of inside DrRacket works better. However, it seems to trigger memory corruption problems, which I don't get with DrRacket (maybe related with this)?

I also don't get this problem on Windows.

For me it feels like the 'garbage collector' kicks in every now and then. I.e. regarding the ‘audio clicks’.