| Showing 1-30 of 1806 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 114661 | 2024-04-16 22:51 | 2024-04-17 10:41 | MySQL Server | Can't repeat (2 days) | S3 | 8.0.30 | Any | Any | ibuf_merge_or_delete_for_page cause crash |
| 114544 | 2024-04-03 12:28 | 2024-04-03 14:07 | MySQL Server | Can't repeat (16 days) | S3 | 8.0.36 | MacOS | ARM | MySQL crash after too many INSTANT DDL |
| 113466 | 2023-12-19 18:31 | 2023-12-20 13:47 | MySQL Server | Can't repeat (121 days) | S3 | 8.0.34 | Windows | x86 | MySQL provides Truncated incorrect DOUBLE value: '0A000' error in trigger |
| 113334 | 2023-12-05 8:32 | 2023-12-05 10:38 | MySQL Server | Can't repeat (136 days) | S2 | 8.0.30 | Windows (2016) | Any (12 CPUs) | Mysql memory bloating and causing server out of memory |
| 112694 | 2023-10-12 0:00 | 2023-11-09 11:50 | MySQL Server | Can't repeat (190 days) | S2 | 8.0.34 | Linux | Any | MYSQL master crashes frequently after upgrade from 8.0.28 to 8.0.34 |
| 112421 | 2023-09-22 1:46 | 2023-09-25 11:02 | MySQL Server | Can't repeat (208 days) | S3 | 8.0.32 | CentOS (7) | Any | zero and null value, left or right join result wrong |
| 112148 | 2023-08-23 3:34 | 2023-08-23 12:53 | MySQL Server | Can't repeat (240 days) | S3 | 8.0.34 | Red Hat (Red Hat Enterprise Linux Server 7.7(Maipo)) | x86 (Hygon C86 7375) | Description Failed to upgrade mysql from 8.0.20 to 8.0.34 |
| 112111 | 2023-08-18 8:54 | 2023-08-18 12:50 | MySQL Server | Can't repeat (245 days) | S3 | 8.1.0 | Any | Any | Incorrect query results on comparing with SOME including some null value |
| 111872 | 2023-07-25 6:46 | 2023-08-15 7:05 | MySQL Server | Can't repeat (248 days) | S3 | 8.0.33 | Red Hat (RHEL 8.8) | x86 | VIEW reference in a SELECT subquery returns different results between 5.7 & 8.0 |
| 111961 | 2023-08-03 18:21 | 2023-08-03 18:32 | MySQL Server | Can't repeat (260 days) | S3 | 8.0.34 | Windows (Windows Server 2019) | Other (x64) | MySQL 8.0.34 crashing suddenly |
| 111946 | 2023-08-02 15:12 | 2023-08-04 12:12 | MySQL Server | Can't repeat (261 days) | S3 | 5.7 | Debian | Any | Fulltext index not being maintained, nothing shows up in error log or mysqlcheck |
| 111442 | 2023-06-15 19:02 | 2023-07-17 12:48 | MySQL Server | Can't repeat (277 days) | S3 | 8.0.32 | Any | Any | misleading startup error message related to GTID configuration |
| 111626 | 2023-06-30 7:09 | 2023-06-30 13:26 | MySQL Server | Can't repeat (294 days) | S3 | 8.0.23-commercial | Any | Any | The MGR configuration is partially incorrect as expected |
| 111420 | 2023-06-14 12:37 | 2023-06-14 13:25 | MySQL Server | Can't repeat (310 days) | S2 | 8.0.32 | Ubuntu | Other | DB instance restarted with AWS RDS database |
| 110345 | 2023-03-11 21:50 | 2023-07-18 12:50 | MySQL Server | Can't repeat (365 days) | S2 | 8.0.32 | MacOS (Ventura 13.0.1) | ARM | MySQL crash on MacOS typically when restoring a MySQL 5.7 sql |
| 110676 | 2023-04-13 8:46 | 2023-04-13 11:52 | MySQL Server | Can't repeat (372 days) | S2 | 8.0.32 | Ubuntu (20.04) | x86 | mysqld got signal 11 after update from 8.0.31 to 8.0.32 |
| 110598 | 2023-04-04 5:40 | 2023-04-04 13:11 | MySQL Server | Can't repeat (381 days) | S3 | 8.0.30 | Windows (Windows Server 2016 Datacenter) | x86 (Intel Xeon Silver 4216) | [ERROR] [MY-013183] [InnoDB] Assertion failure: fsp0fsp.cc:2152:inode thread |
| 110343 | 2023-03-10 22:00 | 2023-03-14 13:07 | MySQL Server | Can't repeat (402 days) | S3 | 8.0.32-1.el8 | Linux (Official MySQL Docker image) | x86 | Reproducible crash with assertion failure when updating |
| 109289 | 2022-12-06 8:20 | 2023-03-06 13:48 | MySQL Server | Can't repeat (410 days) | S3 | 8.0.30, 8.0.32 | Windows (Server 2019) | Any | MySQL 8.0.32 corrupted table causing MySQL to crash |
| 110269 | 2023-03-03 13:28 | 2023-03-03 15:05 | MySQL Server | Can't repeat (413 days) | S3 | 8.0.30 | Ubuntu (Rel 20.04.2) | Any (Intel Xeon E5620) | Server crashed on ALTER TABLE. Now crashes on SELECT. |
| 110014 | 2023-02-10 1:29 | 2023-02-10 13:34 | MySQL Server | Can't repeat (434 days) | S3 | 5.7.38 | CentOS | x86 | Crash during pquery: process_str_arg & my_vsnprintf_ex |
| 109301 | 2022-12-06 23:05 | 2022-12-08 4:36 | MySQL Server | Can't repeat (498 days) | S2 | 8.0.31 | Fedora | Any | MySQL 5.7 -> 8.0.31 Page old data size XXX new data size YYY error |
| 108086 | 2022-08-08 5:39 | 2023-02-06 14:11 | MySQL Server | Can't repeat (518 days) | S2 | Server version: 8.0.30-0ubuntu0.20.04.2 | Ubuntu (20) | Any | Backup crash server - Assertion failure: block->page.get_space() != nullptr |
| 109138 | 2022-11-18 16:24 | 2022-11-18 16:33 | MySQL Server | Can't repeat (518 days) | S3 | 8.0.30 | Ubuntu (22.04.4) | Any | Assertion failure: os0file.cc:2872 |
| 109124 | 2022-11-17 14:58 | 2022-11-22 6:44 | MySQL Server | Can't repeat (518 days) | S1 | 8.0 | Linux (Redhat, CentOS, Kylin) | Any | skip scan retrieves incorrect result after delete |
| 108186 | 2022-08-18 9:28 | 2022-09-19 13:37 | MySQL Server | Can't repeat (578 days) | S3 | 8.0.30 | Ubuntu (20.04) | x86 (AMD Ryzen 7 Pro 5850U) | mysqld got signal 11 when upgrade 8.0.29 to 8.0.30 |
| 108288 | 2022-08-25 22:22 | 2022-08-29 11:51 | MySQL Server | Can't repeat (602 days) | S3 | 8.0.29 | Any | Any | HIGH_NUMBER_OF_BYTES_USED is incorrect |
| 107968 | 2022-07-26 2:36 | 2022-07-26 14:24 | MySQL Server | Can't repeat (633 days) | S3 | Debian | x86 | MySQL crashes with InnoDB errors | |
| 107889 | 2022-07-15 2:14 | 2022-07-15 12:35 | MySQL Server | Can't repeat (644 days) | S1 | 8.0.29 | Linux (Amzon RDS for mysql) | Any | sometimes. when executing UNION querying occurs Signal 11 occures |
| 107053 | 2022-04-19 12:54 | 2022-05-30 11:53 | MySQL Server | Can't repeat (690 days) | S2 | 5.7.34 | Ubuntu (16.04.1 LTS (Xenial Xerus)) | x86 (x86_64) | Restart of mysql unexpectedly |
| Showing 1-30 of 1806 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
