Fixed
Details
Assignee
Michael OffnerMichael OffnerReporter
Michael Born @ OrtusMichael Born @ OrtusPriority
MinorNew Issue warning screen
Before you create a new Issue, please post to the mailing list first https://dev.lucee.org
Once the issue has been verified, one of the Lucee team will ask you to file an issue
Sprint
Affects versions
Details
Details
Assignee
Michael Offner
Michael OffnerReporter
Michael Born @ Ortus
Michael Born @ OrtusPriority
New Issue warning screen
Before you create a new Issue, please post to the mailing list first https://dev.lucee.org
Once the issue has been verified, one of the Lucee team will ask you to file an issue
Sprint
Affects versions
Created 21 December 2022 at 14:47
Updated 6 March 2025 at 11:41
Resolved 4 June 2023 at 10:52
Any ORM session opened in a thread is left opened along with all attached ORM objects. This is the textbook definition of a memory leak, and will eventually result in an OutOfMemory exception if we use threads to do any processing of large ORM entities.
The number of “orphaned” sessions grows with each page request and never decreases. i.e., Lucee never closes these sessions, whether after the request ends or otherwise. Even an
ApplicationStop()
orormReload()
fails to close the open sessions.Once outside the thread, there is no way to reference or close these ORM sessions.