The main goal of randomizing path to temporary profile is to run many profiles simultaneously, not to make it harder to find out the path to that profile. If the path is something like this - "%TEMP%\KM_3861" (where 3861 is random component), than you may run 9999 profiles at the same time without getting potential collisions of sessions.
With your option "-P test2", you may run only one temporary profile and then you have to remember that it's used (or not). With my approach - I don't care (or should remember) which profile I'm using. There are plenty and they're all equal and ready to use at any time. I'm lazy and, as a result, I made BAT file once and then I forget about profile collision problem...
> But, to be fair, it's enough to have a secondary profile with restricted preferences for cookies and other privacy elements, or just deleting the history, cookies files and others.
@JohnHell, I;m sick and tired watching how developers of modern browsers dance around setting/keeping cookies policies. They make it harder and harder to provide users with very simple and effective strategy (which I always use, BTW) - allow only session cookies (with my set of exceptions to keep some of them permanent) and block all third party cookies all the times. My first impression is that K-Meleon does the job well, but I have not checked it against third party cookies yet (and it will take a time to come to a conclusion). On the other hand, approach, that I'm using, is universal for all major browsers (e.g. Firefox, Iron, Chromium) regardless of their cookie policies, that they may currently push on us.
That's why using a temporary profile was the first thing I encounter starting using M-Meleon. I need to run it using profile from a specific folder.
@JohnHell, I'm not familiar with this Forum yet. Could you please move the crash issue via appropriate channels here? Crashing is not an acceptable way for any program to react on its problems. Sending some brief but descriptive enough message to users is... Thanks!