It appears that in some cases, the tag browser eats memory. I was never able to reproduce it, but Kovid got close. The latest release (0.8.7) radically changes how the tag browser works initializes, eliminating (as far as we can tell) the problem.
If you run with the tag browser open, then try the new release. It might help.