Lucee engine reset() kills current thread (regression)

Description

Ticket has had a negative effect on the FusionReactor line performance monitor, which is used by TestBox 3.0 for code coverage reporting. Specifically, this line which seems to kill the currently executing thread:

https://github.com/lucee/Lucee/commit/81f5520f20deeddbc25f811a571a60983c5cf684#diff-2bd4a0f2e5824a28a0ea12b1d5ff663dR41

When Fusionreactor enables the line performance monitor, it issues a reset() of the Lucee engine. I believe this is to clear out any cached class files so it can instrument them when they compile again. The problem is that Lucee kills the request dead when FR issues the reset() call, causing a 500 error to come back.

This causes an error similar to this in the logs:

This can be seen with great consistency like so:

Environment

None

Assignee

Unassigned

Reporter

Brad Wood

Priority

Trivial

Labels

Fix versions

Configure