Avoid accumulating executed search debug traces outside debug mode

[simon-matt-oetztal]

Changes in this pull request

Resolves #417

Prevent SearchExecutionService debug trace accumulation outside debug mode

What

This PR changes SearchExecutionService so that $executedSearches is populated only when Pimcore debug mode is enabled.

Why

SearchExecutionService currently stores per-query SearchInformation including:

• full search response
• debug_backtrace()

In long-running CLI commands this accumulates and causes significant memory growth, although the data is only useful for debugging.

How

In SearchExecutionService::executeSearch():

• wrap both $this->executedSearches[] = ... writes (success + exception path) in:
  • if (Pimcore::inDebugMode()) { ... }

Impact

• Debug/dev behavior: unchanged (query debug information still available).
• Prod/no-debug behavior: avoids unnecessary in-memory accumulation of debug traces.
• No API change.

Motivation / use case

This was observed during long-running data object update/import commands where memory rose steadily due to query trace collection.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud