Close and remove from memory problem

[SparkOut]

This is a bit strange, and I don't know how easy it will be to describe and I doubt it will be reproducible, somehow.

Before I log it as a bug on QC (which it might not "exactly" be) and without being able to give some reproducible details it might be impossible for an engineer to examine, I thought I'd ask here.

The build is 3.0.0-gm-3 of Studio for Windows (running on XP). (It also sits alongside the versions 2.8.1 through to date, although I almost never use those.)

The problem is that on occasions (I don't know how to consistently reproduce it) when closing a stack with the "close and remove from memory" option from the application browser, sometimes the IDE will refuse to remove the stack, and sometimes it will remove the stack, but instead of emptying the application browser it will load up a completely different stack - sometimes one I haven't used for days or even weeks, and not on the recently used history. One in particular seems to be recurrent. The stack and all its cards are shown in the application browser, but they are invisible in the IDE although they will become visible if you choose them from the application browser and "go". Sometimes when the "extra" stack is imported then on closing and removing from memory it will exit, but most often it will hang. It has never yet closed and loaded up another stack though.

Does anyone have any idea if this may be cleared by perhaps flushing some legacy history garbage from a directory somewhere, or is this a more serious IDE bug do you think?

PS all the stacks are set to purge on close