You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Logback integrations run already-formatted log messages through String.format again: a % in a log argument can cause OutOfMemoryError #6715
Both messages reach Sentry exactly as logback formatted them, and the program exits normally:
Sent to Sentry (11 chars): q=PO%2010B
Sent to Sentry (17 chars): q=PO%2006007404B
Actual Result
The first message reaches Sentry corrupted:
%2010B becomes TRUE padded to 2,010 characters.
The second kills the JVM with exit code 3:
Sent to Sentry (2014 chars): q=PO …about 2,000 spaces… TRUE
Terminating due to java.lang.OutOfMemoryError: Java heap space
In our case the input was "PO 06007404B". The %20 came from URL-encoding the space when the request URI was built. Rejecting or stripping % in user input would not have prevented it.
Activity
linear-code commentedon Nov 20, 2026
JAVA-849