Bug#38328780: mysqld fails to start with assertions

Open

#105 opened on Jun 8, 2026 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 4/5
Estimated time: 3-5 days
Newbie friendliness: 48/100

Issue type: Bug
Clarity: Mostly clear
Activity status: Quiet
Tech stack: cpp, mysql
Domain: databases

Research direction

Start by reproducing the early server exit with --skip-grant-tables and the invalid Windows connection parameters, then compare the shutdown sequence with upstream commit 5b35664ed0cdb531b9c8298b81727a527437c12b. Done means the replication tracker and compress GTID threads are ended before plugin shutdown and the InnoDB assertion no longer occurs.

Written by the indexing model from the issue text.

Description

Background:

When server is started with --skip-grant-tables privileges are not
checked. Remote connections are not allowed. In Windows, server has to
be run with TCP/IP, --shared-memory, or --named-pipe should be enabled
to allow remote connections. Otherwise server is not started and exits
execution early with a message that it was started with wrong
parameters.

Problem:

During early return server did not end the replication tracker thread
and compress GTID thread before it started to shut down the plugins as
it is done during normal server shutdown. As a result of that InnoDB
shutdown failed because it detected open transactions from those
threads.

Commit
https://github.com/LiuPlusPlus/TXSQL/commit/e54550dbb6cb3570147a6ca5bb284e824d654e10

Upstream Reference
https://github.com/mysql/mysql-server/commit/5b35664ed0cdb531b9c8298b81727a527437c12b

Dominant language: C++
Stars: 338
Forks: 235
PR merge metrics: No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

[Bug] NULL pointer dereference in llm_running_callback (NGZA-AX-LLM #3) Open

Difficulty 1/5 Under an hour Newbie friendliness 90/100

AXERA-TECH/ax-llm#77 · Opened Sep 22, 2026
resume() sends a second HTTP response (400) after a successful resume Open

Difficulty 1/5 Under an hour Newbie friendliness 90/100

games-on-whales/wolf#509 · Opened Sep 21, 2026
pn7160: reader goes permanently deaf — post-read IRQ-low check fails reads that succeeded Open

Difficulty 2/5 1-3 hours Newbie friendliness 74/100

esphome/esphome#19452 · Opened Sep 21, 2026
Eval bug: Ministral-3 tool-calls during reasoning are not processed Open

bug-unconfirmed

Difficulty 2/5 1-3 hours Newbie friendliness 76/100

ggml-org/llama.cpp#29248 · Opened Sep 21, 2026
run_tests.py fails on windows, but running tests individually works Open

Difficulty 2/5 1-3 hours Newbie friendliness 74/100

NVIDIA/cuda-samples#453 · Opened Sep 21, 2026

More C++ issues