java.lang.OutOfMemoryError: Required array length 2147483638 + 22 is too large #4809
-
Describe the bug
To Reproduce ctags Host Info |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 2 replies
-
The indexer seems to be running with the default Java heap size. The size is listed in the indexer logs near the beginning, unfortunately the logs are trimmed. AOSP is certainly considered a large code base that would require tuning, see https://github.com/oracle/opengrok/wiki/Tuning-for-large-code-bases and note similar tuning ought to be done for the webapp as well. Also, in addition to the tuning consider ignoring potentially huge files with the |
Beta Was this translation helpful? Give feedback.
-
I scroll to the very beginning, seems no java heap size info printed.
Thanks for the tuning guide, I'll look through it. |
Beta Was this translation helpful? Give feedback.
-
My logging file as following, do I need tune something to print logs on console?
BTW, I use the latest opengrok 1.14.1 |
Beta Was this translation helpful? Give feedback.
-
After change the level of log, does it means the java heap size is 19G?
After filter some folders, and adjust java heap size to 32G, it works fine. @vladak Thanks for your guide! |
Beta Was this translation helpful? Give feedback.
The indexer seems to be running with the default Java heap size. The size is listed in the indexer logs near the beginning, unfortunately the logs are trimmed.
AOSP is certainly considered a large code base that would require tuning, see https://github.com/oracle/opengrok/wiki/Tuning-for-large-code-bases and note similar tuning ought to be done for the webapp as well.
Also, in addition to the tuning consider ignoring potentially huge files with the
-i
option.