Bug #109515 Out of memory (Needed 1062936 bytes)
Submitted: 3 Jan 2023 11:03 Modified: 3 Jan 2023 14:33
Reporter: Avinash Chandani Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Server Severity:S2 (Serious)
Version:8.0.30 OS:Windows
Assigned to: CPU Architecture:Any
Tags: Out of memory (Needed 1062936 bytes)

[3 Jan 2023 11:03] Avinash Chandani
Description:
MySQL is getting crashed with Out of memory (Needed 1062936 bytes).
We were facing issues in MySQL 8.0.28 then We have upgraded from MySQL 8.0.30 and still facing same issue.

How to repeat:
Install MySQL 8.0.28
Upgrade to MySQL 8.0.30

Configurations in my.ini file :-

[client]  
[mysql]  
[mysqld]
[mysqld] 
[mysqld]  
back_log=80  
binlog-format=mixed
binlog_row_event_max_size=8K  
character-set-server=utf8mb4
collation-server = utf8mb4_unicode_ci
collation-server=utf8mb4_unicode_ci
default-storage-engine=INNODB  
default_authentication_plugin=mysql_native_password
explicit_defaults_for_timestamp=0
explicit_defaults_for_timestamp=OFF
flush_time=0  
general-log=0
general_log_file="CHAPDA3UTOUM02.log"  
group_concat_max_len=15000
innodb_adaptive_hash_index=OFF
innodb_autoextend_increment=64  
innodb_buffer_pool_instances=8  
innodb_buffer_pool_size=14336M
innodb_checksum_algorithm=0  
innodb_concurrency_tickets=5000  
innodb_file_per_table
innodb_file_per_table=1  
innodb_flush_log_at_trx_commit=2
innodb_flush_log_at_trx_commit=2
innodb_lock_wait_timeout=50
innodb_log_buffer_size=8M
innodb_log_buffer_size=8M
innodb_log_file_size=4301M
innodb_monitor_enable=log_lsn_checkpoint_age,log_max_modified_age_async
innodb_monitor_enable=log_lsn_checkpoint_age,log_max_modified_age_async
innodb_old_blocks_time=1000  
innodb_open_files=300  
innodb_print_all_deadlocks=1
innodb_stats_on_metadata=0  
innodb_thread_concurrency=4
key_buffer_size=8M  
local_infile=ON
log-bin-trust-function-creators=1
log-bin=unified-manager
log-error=error.log
log-output=FILE  
log_error_verbosity=3
log_slow_extra=1
long_query_time=10  
lower_case_table_names=1
max_allowed_packet=1G
max_allowed_packet=1G
max_connect_errors=100  
max_connections=750
max_connections=750
max_heap_table_size=100M
myisam_max_sort_file_size=100G  
myisam_sort_buffer_size=209M
mysqlx=0
net_buffer_length=1M
net_read_timeout=3600
net_write_timeout=3600
open_files_limit=32768
performance_schema_max_digest_length=10240
port=3306
port=3306  
port=3306  
read_buffer_size=64K
read_rnd_buffer_size=256K
relay_log=relay.log
require_secure_transport=ON
server-id=3306
slow-query-log=0
sql-mode=STRICT_TRANS_TABLES,NO_ENGINE_SUBSTITUTION
sync-binlog=1
sync_master_info=10000  
sync_relay_log=10000  
sync_relay_log_info=10000  
table_definition_cache=8000
table_open_cache=10000
thread_cache_size=150
thread_cache_size=150
tls_version=TLSv1.2
tmp_table_size=100M
tmp_table_size=100M
transaction-isolation=READ-COMMITTED
[3 Jan 2023 14:33] MySQL Verification Team
Hi Mr. Chandani,

Thank you for your bug report. However .........

Not enough information was provided for us to be able to handle this bug. Please re-read the instructions at http://bugs.mysql.com/how-to-report.php 

If you can provide more information, feel free to add it to this bug and we shall  change the status back to 'Open'.  

In order to do so, we need a fully repeatable test case, which should consist of a set of SQL statements that are always leading to the OOM conditions.

Based on what you have provided , we can only concluded that your MySQL server is misconfigured, which is not a bug. All configuration options are described in our Reference Manual.

Thank you for your interest in MySQL.

Can't repeat ........