[GC (CMS Initial Mark) [1 CMS-initial-mark: 171127K(180224K)] 237229K(253952K), 0.0163927 secs] [Times: user=0.02 sys=0.00, real=0.02 secs]
[CMS-concurrent-mark-start]
[CMS-concurrent-mark: 0.035/0.035 secs] [Times: user=0.11 sys=0.00, real=0.03 secs]
[CMS-concurrent-preclean-start]
[CMS-concurrent-preclean: 0.002/0.002 secs] [Times: user=0.00 sys=0.00, real=0.00 secs]
[CMS-concurrent-abortable-preclean-start]
CMS: abort preclean due to time [CMS-concurrent-abortable-preclean: 0.949/5.009 secs] [Times: user=0.48 sys=0.01, real=5.00 secs]
[GC (CMS Final Remark) [YG occupancy: 67144 K (73728 K)][Rescan (parallel) , 0.0086168 secs][weak refs processing, 0.0011738 secs][class unloading, 0.0082043 secs][scrub symbol table, 0.0184540 secs][scrub string table, 0.0009106 secs][1 CMS-remark: 171127K(180224K)] 238272K(253952K), 0.0374969 secs] [Times: user=0.08 sys=0.02, real=0.03 secs]
[CMS-concurrent-sweep-start]
[CMS-concurrent-sweep: 0.044/0.044 secs] [Times: user=0.05 sys=0.00, real=0.06 secs]
[CMS-concurrent-reset-start]
[CMS-concurrent-reset: 0.000/0.000 secs] [Times: user=0.00 sys=0.00, real=0.00 secs]
#系统正常运行一定时间后会出现这样的情况，就是CMS标记一直无限重复，如果在重复时间段调用一个数据量较大的接口就会导致java heap space。但是系统中并不存在较大数据量传入传出的接口，目前来看可能是有某个地方一直在生成对象，但系统中的流已经关闭（测试问题的时候甚至包含流的接口都已经注释掉），递归层数也很小且数据量也很小，之前类似的项目发现问题在于框架层对于每条传入的数据都要经过权限接口审核，目前新版框架已经关闭该审核但还是会出现该问题，求解答
