MySQL Bugs: #80523: current_memory in sys.session can go negative!

Bug #80523	current_memory in sys.session can go negative!
Submitted:	26 Feb 2016 9:23	Modified:	26 Feb 2016 10:50
Reporter:	Shane Bester (Platinum Quality Contributor)	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Server: Performance Schema	Severity:	S3 (Non-critical)
Version:	8.0.0, 8.0.11	OS:	Windows
Assigned to:	Marc ALFF	CPU Architecture:	Any

File:	Maximum allowed size is 3MB.
Description:
Privacy:

If the data you need to attach is more than 3MB, you should create a compressed archive of the data and a README file that describes the data with a filename that includes the bug number (recommended filename: mysql-bug-data-80523.zip) and upload one to sftp.oracle.com. A free Oracle Web (SSO) account (the one you use to login bugs.mysql.com) and a client that supports SFTP are required in order to access the SFTP server.

To upload the file to sftp.oracle.com:

Open an SFTP client and connect to sftp.oracle.com. Specify port 2021 and remote directory /support/incoming/.
Log in with your newly created Oracle Web account (email address) and password.
Upload the archive to /support/incoming.
Once you have uploaded the file, add a comment to this bug to notify us about it.

Example: sftp -oPort=2021 -oUser=email sftp.oracle.com:/support/incoming

Usage Notes: This directory is unlistable, which means that once you have uploaded your file, you will not be able to see it. A file cannot be uploaded more than once with the same filename. The filename must be changed before attempting to upload the file again. The filename should always start with mysql-bug- prefix. Files are retained on the SFTP server for 7 days and then permanently removed.

complete outputs

Attachment: bug80523_output.txt (text/plain), 1.25 MiB.

current_memory is negative

Attachment: session-20201230.log (application/octet-stream, text), 279.62 KiB.