#106593Deadlock in Typo3DatabaseBackend::set() on concurrent invocations
Description
Description
If Typo3DatabaseBackend::set() is called many times concurrently database deadlock exceptions occur.
A reproduction example is available on GitHub: https://github.com/adamkoppede/reproduce-deadlock-with-fluidtypo3-vhs-7-1
Background
fluidtypo3/vhs 7.1.1 calls Typo3DatabaseBackend::set() four times per request in certain situations: TODO downstream reference
Reviews 1
History 15
-
Gerrit Code Review pushed patch set 1 for main to change 89179 status
NewUnder Review <span data-processor="relativetime" data-value="2025-04-21T21:45:53+00:00" > 04/21/25, 21:45 </span> -
Gerrit Code Review pushed patch set 2 for main to change 89179 <span data-processor="relativetime" data-value="2025-04-24T20:02:28+00:00" > 04/24/25, 20:02 </span>
-
Gerrit Code Review pushed patch set 3 for main to change 89179 <span data-processor="relativetime" data-value="2025-11-07T18:50:57+00:00" > 11/07/25, 18:50 </span>
-
Gerrit Code Review pushed patch set 4 for main to change 89179 <span data-processor="relativetime" data-value="2026-04-22T11:05:22+00:00" > 04/22/26, 11:05 </span>
I cannot find the option to update the description.
The issue in the downstream fluidtypo3/vhs GitHub bug tracker is https://github.com/FluidTYPO3/vhs/issues/1945.
There are also sometimes multiple cache_<ident> rows for the same cache entry identifier. But Typo3DatabaseBackend::get() always fetches a single row only. So it seems that there should only be one row per cache entry identifier.</ident>