Instance of lucee.runtime.debug.DebuggerPool in retained heap, even though debugging turned off

Description

A heap dump showed half the retained heap on a server (which was total around 700MB) was taken by a single instance of lucee.runtime.debug.DebuggerPool. I checked and debugging was turned off in the server context and in the web context (it likely was previously turned on some hours before the heap dump was taken).

Can provide the heap dump separately if required. See screenshot below from MAT.

Environment

None

Attachments

1

Activity

Show:

Zac Spitzer 19 May 2021 at 10:42

I think this has been fixed, part of the cause was including scopes in the debugging logs, which blew out memory usage

Unresolved

Details

Assignee

Reporter

Priority

Labels

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 25 April 2019 at 08:34
Updated 19 May 2021 at 10:42