StackoverflowError when generating offline symbol table.

[Former user]

Hello,

on a specific project, which contains a lot of classes, I get the following error message when I generate the offline symbol table :

‌

Illuminated Cloud build number : 20210727162526

Illuminated Cloud version : 2.1.8.5

IDEA build number : #IU-211.7628.21

IDEA version : 2021.1.3

Operating System : Windows 10 Professional 64 bit

‌

I tried so far to increase IntelliJ’s Java Heap size as well as Java compiler allocated memory but none worked.

Thank you in advance for you assistance,

‌

Best regards,

Arsène Lapostolet

[Scott Wells]

Thanks. There's really no good reason for a StackOverflowError during OST generation, so I'm guessing it's a bug. Let me take a look at the provided log and see what I can find.

[Scott Wells]

So the only places that I see Json serialization occurring in the step where this is failing are in debug/trace logging, and I notice that you have that enabled. Can you please open Help>Diagnostic Tools>Debug Log Settings and either remove entries for OST generation or minimally removing the leading #s, e.g., the following would be fine:

com.illuminatedcloud.symtab.OfflineSymbolTable
com.illuminatedcloud.symtab.OfflineSymbolTable!trace
com.illuminatedcloud.intellij.settings.project.OfflineSymbolTableGenerator
com.illuminatedcloud.symtab.SystemDeclarations

Then try to regenerate the OST and let me know if you continue to have issues.

[Former user]

I disabled the logs you mentioned and the issue is gone !
I feel dumb since I enable those logs to help troubleshoot another issue but forgot to disable them.

Thank you for your time and sorry since this was my mistake.

Thanks you also for your fast and efficient support, like always !

Have a nice day

[Scott Wells]

Well, there's certainly an irony (in the very real sense of that word) that enabling diagnostic logging causes a failure! I'll investigate that a bit and minimally ensure that debug/trace logging doesn't kill the entire process.

[Scott Wells]

Resolving this but will address the potential failure when logging.