Not that this will happen too often, but it might point to a "memory/resource" issue.
if you open a project, then within the environment open another "recent" project, then open the first, now "recent" project, then open the other...after a couple of iterations, B4a blows up with a memory issue.
I have the same issue with my app.
I did notice that if you don't execute/swap too quick from a screen to another,
it'll be fine.
But unfortunately users don't think about that, so 'force close' will be inevitable.
That is correct, Erel.
It occurs only in the environment.
It is not a big problem, but I thought you should know. There is (likely) a memory leak somewhere.