COMMIT WORK executed by system

What causes this issue?

You are in the ABAP Debugger. The system tried (unsuccessfully) to
switch the work process to debugging mode.

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

There are currently so many processes operating in debugging mode in
this system that <ZH>it was not possible to switch this process into
debugging mode as well</>. The system therefore executed a commit.
In production (Customer) systems or clients, the commit is not executed
for security reasons. Instead, the system prevents debugging.
You are not working in a production client (see table T000). The
maximum number of work processes that may work in debugging mode is set
in the profile parameter rdisp/wpdbug_max_no.
Dialog work processes working in debugging mode are assigned to a
single user; this protects the user context from any process changes.
Usually, user contexts are rolled out of the old work process when the
system is waiting for user input, and prepared to be rolled into a new
work process. A commit is then required.
Work processes in debugging mode cannot be used by other users. The
number of free work processes is therefore reduced, and this can affect
system performance. For this reason, there is a limit on the number of
work processes which can be in debugging mode at any time.

System Response

How to fix this error?

Changes to tables are written to the database in the COMMIT WORK. Note
this when working with the ABAP Debugger, particularly when you want to
exit the debugger. It is often safer to let the program run on until
the next screen is displayed.
The system will switch the dialog process with which you are working
into debugging mode as soon as possible.

Error message extract from SAP system. Copyright SAP SE.