Closed mark8s closed 2 weeks ago
Is there any exception stack trace on server stdout/err?
Could you provide the gc log so I can reproduce this problem in my env?
@D-D-H How do I send you?
@mark8s
Could you attach the log here?
![Uploading image.png…]()
@mark8s
I cannot reproduce the problem.
Can you provide your running config(jvm options, jifa application.yml)?
@D-D-H OK,tks~, I'm not free these days, I'll check it again, maybe there's something wrong with my configuration. Or can you show me your configuration?
I just used the default config.
@D-D-H How did you run it? Does it have anything to do with the performance of the machine? This seems to be a code problem. I didn't change anything. What version of jifa are you running?
@D-D-H I reproduced this problem. When I started a master node and a static node, the problem seemed to occur when the static node returned results. Because this error did not occur when I parsed in standalone-worker mode. When I parsed the heap dump using multiple nodes, I also encountered this error. Only Object Group did not have an error. The other three all showed the same error message.
@D-D-H @mark8s I fixed this issue in this #311 . The reason this error occurred was because the default buffer byte size in Spring is 256KB (262144 bytes). After I modified it to 10MB, the error no longer appears.
@mycxu ok~
The PR is merged.
When I perform GC log analysis, this error is reported. Is it because my GC file size is too large? Is there a way to solve it?