| Showing all 28 (Edit, Save, CSV, Feed) |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 21487 | 2006-08-07 18:15 | 2006-09-22 9:23 | MySQL Server | Not a Bug (6419 days) | S1 | 5.0.24,4.1.21,4.0.26 | Windows (windows) | Any | Handle Leak on mysqld-nt.exe when using query cache |
| 24745 | 2006-12-01 7:00 | 2007-01-04 16:17 | MySQL Server: InnoDB storage engine | Can't repeat (6315 days) | S3 | 4.0.26, 5.0.38 | Linux (Linux) | Any | InnoDB semaphore wait timeout/crash - deadlock waiting for itself |
| 25645 | 2007-01-16 10:19 | 2011-02-16 23:43 | MySQL Server: InnoDB storage engine | Closed (5054 days) | S1 | 5.0.26 | Linux (linux Red Hat) | Any | Assertion failure in file srv0srv.c; adaptive hash hang in a complex query |
| 30642 | 2007-08-27 7:34 | 2008-04-14 18:21 | Connector / NET | Closed (5849 days) | S2 | 5.0.8.1 | Windows (XP SP 2 and 2003 Server) | Any | Adding the given count to the semaphore would cause it to exceed its maximum cou |
| 31511 | 2007-10-10 17:55 | 2013-08-25 20:45 | MySQL Server: InnoDB storage engine | No Feedback (5958 days) | S2 | 5.0.37-community-nt | Windows (XP Professional SP2) | Any | MySQL Instance crashes after a long semaphore wait. |
| 32873 | 2007-11-30 11:53 | 2013-02-20 22:21 | Connectors: DBD::mysql ( Perl ) | Unsupported (4076 days) | S3 | 5.0.45 (DBD::mysql 3.0002) | Windows (XP SP2) | Any | Semaphore object left open after database handle closes in Perl::DBD on windows |
| 33682 | 2008-01-03 23:16 | 2008-07-08 14:09 | Connector / NET | Closed (5764 days) | S1 | 1.0.10+ | Linux | Any | Patch: Semaphore class is Windows only preventing mono from using connector |
| 32149 | 2007-11-06 18:29 | 2011-02-16 23:43 | MySQL Server: Locking | Closed (5411 days) | S2 | 5.0 | Any | Any | Long semaphore wait for adaptive hash latch |
| 32157 | 2007-11-07 5:32 | 2016-01-03 20:45 | MySQL Server: InnoDB storage engine | Duplicate (6005 days) | S3 | 5.0.37 | Linux | Any | Crash from a long semaphore wait on Innodb checkpoint lock |
| 34953 | 2008-02-29 4:18 | 2008-05-11 11:00 | MySQL Server | No Feedback (5822 days) | S1 | 5.0.51a, 5.0.54 | Linux (2.6.9-55.0.9.ELsmp x86_64) | Any | Innodb semaphore problems: MySQL opens a table in the middle of a query |
| 38750 | 2008-08-12 14:21 | 2008-09-13 11:40 | MySQL Server: InnoDB storage engine | No Feedback (5697 days) | S1 | 5.0.51b | Windows (SP2) | Any | Server crashes due to long semaphore wait > 600 seconds |
| 36688 | 2008-05-13 13:24 | 2008-07-22 16:04 | Connector / NET | Closed (5750 days) | S2 | 5.1.6 | Windows (XP SP2 & Vista) | Any | SemaphoreFullException when closing application |
| 41506 | 2008-12-16 14:00 | 2011-02-16 23:43 | MySQL Server: InnoDB storage engine | No Feedback (5198 days) | S1 | 5.0.22 | Linux (Ubuntu 6.06/x86_64) | Any | InnoDB hang on purge_sys->latch in row0vers.c:107 and trx0purge.c:1059 |
| 43671 | 2009-03-16 9:56 | 2011-02-16 23:43 | MySQL Server: InnoDB storage engine | No Feedback (5199 days) | S2 | 5.0.56sp1 | Linux (x86_64) | Any | InnoDB hang on rseg->mutex in trx0trx.c:1846 and trx0roll.c:934 |
| 45082 | 2009-05-26 3:52 | 2009-06-16 8:10 | MySQL Server | Not a Bug (5421 days) | S2 | 5.0.41-log | Linux (Linux 2.6.18-8.1.15.el5 #1 SMP Mon Oct 22 08:32:28 EDT 2007 x86_64) | Any | mysql crash because of a long semaphore wait |
| 47814 | 2009-10-04 18:33 | 2011-02-16 23:44 | MySQL Server: InnoDB storage engine | Closed (5053 days) | S2 | 5.0.44 | Linux | Any | Diagnostics are frequently not printed after a long lock wait in InnoDB |
| 61536 | 2011-06-16 13:46 | 2013-01-30 14:21 | MySQL Server: InnoDB storage engine | Not a Bug (4097 days) | S2 | 5.5.12, 5.5.16 | Windows (Windows XP 64bit) | Any | MySQL intentional server crash on semaphore wait from INSERT |
| 69667 | 2013-07-04 7:26 | 2014-07-21 17:56 | MySQL Server | Can't repeat (3560 days) | S2 | 5.5.31 | Linux | Any | Long semaphore wait crash |
| 66402 | 2012-08-15 16:14 | 2014-04-01 1:00 | MySQL Server: InnoDB storage engine | No Feedback (3675 days) | S2 | 5.5.21-55-log Percona | Linux | Any | Thread locks itself out with semaphore (crash) |
| 74743 | 2014-11-07 20:57 | 2014-11-07 21:53 | MySQL Server | Duplicate (3451 days) | S1 | 5.5.40 | Linux (Debian Wheezy) | Any | MySQL crashing after long semaphore wait |
| 87302 | 2017-08-03 12:23 | 2017-08-04 10:29 | MySQL Server: InnoDB storage engine | Not a Bug (2450 days) | S2 | 5.6.32 | CentOS (2.6.32-279.el6.x86_64) | Any | Data load and index creation taking time |
| 86116 | 2017-04-27 16:19 | 2017-04-27 18:51 | MySQL Server | Duplicate (2549 days) | S1 | 5.7.16 | Windows (Windows 2012) | Any | [ERROR] [FATAL] InnoDB: Semaphore wait has lasted > 600 seconds. |
| 88110 | 2017-10-16 15:54 | 2017-10-16 16:05 | MySQL Server: Locking | Duplicate (2377 days) | S2 | 5.6.36-82 | CentOS (6.8 Final) | Any | Error: semaphore wait has lasted > 600 seconds, and forcing recovery |
| 89515 | 2018-02-02 23:19 | 2018-02-28 13:07 | MySQL Server | Closed (2243 days) | S2 | mysqld 5.7.21-0ubuntu0.16.04.1 | Ubuntu (Welcome to Ubuntu 16.04.3 LTS (GNU/Linux 4.4.0-1050-aws x86_64)) | Any | ALTER TABLE Fails, then all subsequent schema operations fail |
| 71647 | 2014-02-10 8:22 | 2018-03-21 1:00 | MySQL Server | No Feedback (2222 days) | S1 | 5.6.16 | Linux (CentOS 6, 64bit) | Any | Crash: Semaphore wait |
| 77319 | 2015-06-11 15:03 | 2019-10-15 1:00 | MySQL Server | No Feedback (1649 days) | S3 | 5.6.25 | Linux | Any | InnoDB: Warning: a long semaphore wait:Thread xxx has waited at trx0 |
| 97379 | 2019-10-25 8:03 | 2019-11-04 15:32 | MySQL Server: InnoDB storage engine | Not a Bug (1638 days) | S3 | 8.0.18 | CentOS (7.0) | x86 (x86_64) | Semaphore wait has lasted > 600 seconds,then server crash |
| 98295 | 2020-01-20 11:00 | 2023-02-01 7:55 | MySQL Server: InnoDB storage engine | Closed (1535 days) | S3 | 5.7.23 | Any | Any | Innodb internal deadlock cause a long wait semaphore, and a mysqld crash |
| Showing all 28 (Edit, Save, CSV, Feed) |
