When I was using Emacs, I wrote a simple project management system. Every project had its own folder in .emacs.d that contained: 1) *.el config, 2) list of open buffers and their positions, 3) persistent variables. Having implemented that, I've also wrote a simple wrapper that let me to load Emacs with specific project opened. For example, I could fire "emacs kep" to work on my Scala project and, simultaneously, open "emacs pap" to compose latex slides for a talk. Every instance of Emacs would then have its own scratchpad and everything would work finely.
When I tried to reimplement this use case with Sublime, I stumbled upon a problem. Whenever I opened one project (say, "sublime --project foo.sublime-project") after another (say, "sublime --project bar.sublime-project"), Sublime would pick a session from that another project (in our case, from bar). What could be the problem? Is it Session.sublime-session being a bottleneck?