Issue Bug Under Review Orphaned

#106593Deadlock in Typo3DatabaseBackend::set() on concurrent invocations

Adam Koppe 04/21/25, 20:41 updated 04/22/26, 11:05

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

  1. Adam Koppe commented <span data-processor="relativetime" data-value="2025-04-21T21:17:00+00:00" > 04/21/25, 21:17 </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>