IntelliJ crash & burn on regenerate OST with Parallel Processing

[June Bischoff]

I'm about to log an incredibly unhelpful ticket!

Two of our developers had their projects wiped and IntelliJ crashed to the point of needing to reinstall after regenerating their OSTs using the Parallel Processing. Unfortunately, they uninstalled and reinstalled already, so any log files were lost.

I've since regenerated my OST with Parallel Processing without any issue at all. The only clue I have is that I did a Full regen, and they may have done SObjects only.

I'm not really willing to risk the reinstallation to confirm or deny this theory, but I figured I'd log the bug and you can close it as unable to reproduce if SObjects/Parallel Processing doesn't cause you any troubles.

[Scott Wells]

Not unhelpful at all. It tells me that this can happen and that I need to figure out why, and it gives me some direction as to what might cause it. I agree with you that you should try to avoid it happening to you until I can do a little research. I'll try to see if I can come close to reproducing it. My initial gut reaction is that perhaps your large org is resulting in too many simultaneous threads in the IntelliJ process. I'm using the host IDE's thread pooling mechanism, so I'll start there and see how it's managing that pool and what I might to do to constrain it if/when necessary.

Let me see what I can find, and if some useful diagnostic info does emerge, please pass it on. In the interim, I really do apologize for the crash-and-burn that your developers experienced and the resulting lost time.

[Scott Wells]

At some point long ago I constrained the number of concurrent threads. If this is actually still happening, please let me know, but hopefully by capping the thread pool size it shouldn't be.