Malformed multipart message causes memory leak in direct memory (ByteBuf.release() was not called) #33741
Labels
in: web
Issues in web modules (web, webmvc, webflux, websocket)
status: duplicate
A duplicate of another issue
Uh oh!
There was an error while loading. Please reload this page.
When using WebClient with codec MultipartHttpMessageReader/DefaultPartHttpMessageReader parts that only consist of a new line will cause a memory leak in direct memory. The corresponding Netty ByteBuf will not be released.
The extra new line (CR + LF) in part "text-part" causes the memory leak. When any amount of characters are added to this line the MultiPartParser will detect it as content and does release ByteBuf.
The text was updated successfully, but these errors were encountered: