Shutting down and restarting ghci is my current workaround. I was hoping for something a bit less disruptive. :kickoffGC or something like that.

On Mon, Jun 25, 2012 at 6:54 AM, Ketil Malde <ketil@malde.org> wrote:

Jonathan Geddes <geddes.jonathan@gmail.com> writes:

> Is this a known issue? More importantly, is there a known workaround?

My experience is that ghci (typically run as an inferior Emacs process)
often retains a lot of memory. Thus, I occasionally kill and
restart it. (Not sure if that counts as a workaround :-)

-k
--
If I haven't seen further, it is by standing in the footprints of giants