Status/Resolution/Reason: Closed/Withdrawn/CannotReproduce
Reporter/Name(from Bugbase): Peter Boughton / Peter Boughton (Peter Boughton)
Created: 10/17/2014
Versions: 11.0
Failure Type: Memory Leak
Found In Build/Fixed In Build: CF11_Final /
Priority/Frequency: Major / All users will encounter
Locale/System: ALL / Platforms All
Vote Count: 0
Dumping variables from a non-trivial ORM application will causing a java.lang.OutOfMemoryError caused by too many levels of ORM relationships attempting to be resolved.
The only way to prevent the OoM error is by using the top attribute of cfdump/writedump, but even setting top as low as 3 or 4 can still causes crashes, and makes dealing with arrays and nested structs a massive PITA.
There should be a new dump attribute/argument for ormlevels, as well as a global default configurable in the admin, which determines how many levels of relationship should be resolved when dumping/serializing an ORM object.
----------------------------- Additional Watson Details -----------------------------
Watson Bug ID: 3840599
External Customer Info:
External Company:
External Customer Name: boughtonp
External Customer Email:
External Test Config: My Hardware and Environment details:
Attachments:
Comments: