lkishalmi commented on issue #4065: URL: https://github.com/apache/netbeans/issues/4065#issuecomment-1128400539
Try to check at ```/var/log/kern.log```. We have removed the memory settings from NetBeans command line a few years ago. AFAIK java uses the 1/4th of the system memory (maxed at 4 Gb), for default max heap size. You can try to reduce that number by passing -J-Xmx2g to the command line (2g is just an example, of course), so OOM killer would less likely target that process. Also you might check the Gradle daemons and the started Gradle daemon processes they could be memory hungry too. Well, I could discuss this in more detail if you wish, though I do not think NetBeans could do anything about the OOM killer reaping it. If you'd use the Snap version you could try: ``` snap set system resilience.vitality-hint=netbeans ``` So the OOM killer would less likely take actions against the NetBeans Snap Source: https://snapcraft.io/docs/system-options -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
