Open
Description
In examining an OOM heap dump from a 7.12 user it was apparent that the culprit was a rogue document that introduced 360k(!) new fields and had a bunch of TextFieldMapper objects held in o.e.index.mapper.ParseContext.InternalParseContext.dynamicMappers
that together consumed 1.5GB of RAM of 2GB heap.
I know we have circuit breakers for numbers of fields in mappers but perhaps these objects are allocated during parsing before we test that condition?
Either way seems like we need some added robustness here.