Just had one. Not as strange as most of these but annoying. We have a custom P4V tool which often needs to be run simultaneously for two different changelists v

Just had one. Not as strange as most of these but annoying. We have a custom P4V tool which often needs to be run simultaneously for two different changelists via the changelist context menu. However, we noticed that after the first instance of the script finishes on the first changelist the second one running in parallel exits along with the first, never finishing the work for the second changelist. I noticed that if you terminate the second started instance the first is unaffected, only the other way around. At first I thought it was something wrong with handling multiple processes in our tool, or some weird multiprocess tkinter or cx_Freeze issue. Then I realized that starting these two instances of the script from two _separate_ p4v windows resolves the issue and they can run at the same time, not hindering each other. But we can't ask users to have multiple P4V windows open just to run this on multiple changelists. The workaround, for now, is having the custom tool run a batch file instead which then runs the frozen python app exe, ensuring that each actual instance of the tool starts in its own parent process and not as a p4v subprocess.