java.lang.OutOfMemoryError

GC overhead limit exceeded

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web1485

  • via Terracotta by aqt, 11 months ago
    GC overhead limit exceeded
  • via Terracotta by tylercal, 11 months ago
    GC overhead limit exceeded
  • via Terracotta by JavaRef, 11 months ago
    GC overhead limit exceeded
  • Stack trace

    • java.lang.OutOfMemoryError: GC overhead limit exceeded at org.msgpack.io.BufferedOutput.allocateNewBuffer(BufferedOutput.java:37) at org.msgpack.io.BufferedOutput.write(BufferedOutput.java:69) at org.msgpack.io.LinkedBufferOutput.write(LinkedBufferOutput.java:22) at org.msgpack.packer.MessagePackPacker.writeByteArray(MessagePackPacker.java:204) at org.msgpack.packer.MessagePackPacker.writeString(MessagePackPacker.java:236) at org.msgpack.packer.AbstractPacker.write(AbstractPacker.java:191) at org.msgpack.template.StringTemplate.write(StringTemplate.java:38) at org.msgpack.template.StringTemplate.write(StringTemplate.java:25) at org.msgpack.template.AbstractTemplate.write(AbstractTemplate.java:27) at org.msgpack.packer.AbstractPacker.write(AbstractPacker.java:203) at org.fluentd.logger.sender.Event$EventTemplate.write(Event.java:76) at org.fluentd.logger.sender.Event$EventTemplate.write(Event.java:55) at org.msgpack.template.AbstractTemplate.write(AbstractTemplate.java:27) at org.msgpack.MessagePack.write(MessagePack.java:196) at org.fluentd.logger.sender.RawSocketSender.emit(RawSocketSender.java:140) at org.fluentd.logger.sender.RawSocketSender.emit(RawSocketSender.java:129) at org.fluentd.logger.sender.RawSocketSender.emit(RawSocketSender.java:124) at org.fluentd.logger.FluentLogger.log(FluentLogger.java:101) at org.fluentd.logger.FluentLogger.log(FluentLogger.java:86)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.