Report this error OutOfMemoryError procedure, how to find the reason-CodePudding

Program reported this error, the production, the need to do to locate the reason, find out the problem of code

 Java. Lang. OutOfMemoryError: GC overhead limit exceeded 
The at Java. Util. Arrays. CopyOfRange (Arrays. Java: 3664) 
The at Java. Lang. String. & lt; init> (String) Java: 207) 
The at Java nio. HeapCharBuffer. ToString (HeapCharBuffer. Java: 567) 
The at Java nio. CharBuffer. ToString (CharBuffer. Java: 1241) 
At com. Mysql. JDBC. StringUtils. ToString (StringUtils. Java: 2195) 
At com. Mysql. JDBC. Field. GetStringFromBytes (635) Field. Java: 
At com. Mysql. JDBC. Field. GetName (554) Field. Java: 
At com. Mysql. JDBC. Field. GetColumnLabel (486) Field. Java: 
At com. Mysql. JDBC. ResultSetMetaData. GetColumnLabel (ResultSetMetaData. Java: 224) 
At com. Alibaba. Druid. Filter. FilterChainImpl. ResultSetMetaData_getColumnLabel (FilterChainImpl. Java: 4625) 
At com. Alibaba. Druid. Filter. FilterAdapter. ResultSetMetaData_getColumnLabel (FilterAdapter. Java: 2778) 
At com. Alibaba. Druid. Filter. FilterChainImpl. ResultSetMetaData_getColumnLabel (FilterChainImpl. Java: 4622) 
At com. Alibaba. Druid. Filter. FilterAdapter. ResultSetMetaData_getColumnLabel (FilterAdapter. Java: 2778) 
At com. Alibaba. Druid. Filter. FilterChainImpl. ResultSetMetaData_getColumnLabel (FilterChainImpl. Java: 4622) 
At com. Alibaba. Druid. Filter. FilterAdapter. ResultSetMetaData_getColumnLabel (FilterAdapter. Java: 2778) 
At com. Alibaba. Druid. Filter. FilterChainImpl. ResultSetMetaData_getColumnLabel (FilterChainImpl. Java: 4622) 
At com. Alibaba. Druid. Proxy. JDBC. ResultSetMetaDataProxyImpl. GetColumnLabel (ResultSetMetaDataProxyImpl. Java: 107) 
The at org. Apache. Ibatis. Executor. The resultset. ResultSetWrapper. & lt; init> (ResultSetWrapper. Java: 59) 
The at org. Apache. Ibatis. Executor. The resultset. DefaultResultSetHandler. GetFirstResultSet (DefaultResultSetHandler. Java: 239) 
The at org. Apache. Ibatis. Executor. The resultset. DefaultResultSetHandler. HandleResultSets (DefaultResultSetHandler. Java: 176) 
The at org. Apache. Ibatis. Executor. Statement. PreparedStatementHandler. Query (PreparedStatementHandler. Java: 64) 
The at org. Apache. Ibatis. Executor. Statement. RoutingStatementHandler. Query (RoutingStatementHandler. Java: 79) 
The at org. Apache. Ibatis. Executor. SimpleExecutor. DoQuery (SimpleExecutor. Java: 63) 
The at org. Apache. Ibatis. Executor. BaseExecutor. QueryFromDatabase (BaseExecutor. Java: 325) 
The at org. Apache. Ibatis. Executor. BaseExecutor. Query (BaseExecutor. Java: 156) 
The at org. Apache. Ibatis. Executor. CachingExecutor. Query (CachingExecutor. Java: 109) 
The at org. Apache. Ibatis. Executor. CachingExecutor. Query (CachingExecutor. Java: 83) 
At sun. Reflect. GeneratedMethodAccessor73. Invoke (Unknown Source) 
At sun. Reflect. DelegatingMethodAccessorImpl. Invoke (43) DelegatingMethodAccessorImpl. Java: 
The at Java. Lang. Reflect. Method. Invoke (498) Method. The Java: 
The at org. Apache. Ibatis. Plugin. Invocation. Proceed (49) Invocation. Java: 
At com. Making. Pagehelper. SqlUtil. _processPage (SqlUtil. Java: 351)

CodePudding user response:

Did you returned from the database data volume is too big, didn't have caused by paging?

If judging from the code is not the reason, can the heap dump out and see what object inside now most,

General oom, produces the hprof files, take out you use the tool to analysis

CodePudding user response:

Query result in large amount of data memory, paging