Put out the GC detailed log and observe the memory GC situation
Dump the memory snapshot at that time and observe which objects occupy the memory
PS: It is estimated that there are large objects. The large objects directly enter the old generation and still hold references to the large objects in the application
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
Your sql connection is neither reused nor closed...
There is a way to treat the symptoms but not the root cause, which is to increase the memory of the jvm.
Startup parameters Riga-Xms512m-Xmx1024m
Put out the GC detailed log and observe the memory GC situation
Dump the memory snapshot at that time and observe which objects occupy the memory
PS: It is estimated that there are large objects. The large objects directly enter the old generation and still hold references to the large objects in the application
My friends helped me guess the conclusion, you can give it a try
http://www.yl1001.com/group_article/1721468995450102.htm?classic_id=7691469068392318#comment_7691469068392318