# Finding the path of a loaded module

**URL:** <https://racket.discourse.group/t/finding-the-path-of-a-loaded-module/4122>\
**Category:** General\
**Created:** [February 22, 2026, 6:55pm UTC](https://racket.discourse.group/t/finding-the-path-of-a-loaded-module/4122 "2026-02-22T18:55:37Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![hnmdijkema](https://yyz2.discourse-cdn.com/free1/user_avatar/racket.discourse.group/hnmdijkema/32/2629_2.png) [@hnmdijkema](https://racket.discourse.group/u/hnmdijkema)\
**Post date:** [February 26, 2026, 11:32am UTC](https://racket.discourse.group/t/finding-the-path-of-a-loaded-module/4122/8 "2026-02-26T11:32:42Z")

</div>

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](https://racket.discourse.group/t/racket-crashes-with-invalid-memory-reference/2206))?

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’.

---

_[View the full topic](https://racket.discourse.group/t/finding-the-path-of-a-loaded-module/4122)._