Bug #34193: extGetNumberOfCachedPages provokes an allocate memory error - TYPO3 Core - TYPO3 Forge

Custom queries

12 LTS
Accessibility
Dashboard issues
Easy tasks
Extbase Issues
FAL Issues
FAL Sprint 2023
Hierarchical Issues
Issues reported for v11
JavaScript issues
JavaScript Issues (w/o Epics/Stories)
Most wanted Bugfixes
Most wanted Features
My open issues
New & Unassigned
No feedback within 90 days
Open Bugs
Open issues of 10
Page Tree Regressions after 2020-07-28
Recently modified
Regressions
Stabilization Issues
Usability or UX

Actions

Copy link

Bug #34193

closed

extGetNumberOfCachedPages provokes an allocate memory error

Added by Leon Dietsch about 12 years ago. Updated over 5 years ago.

Status:

Closed

Priority:

Should have

Assignee:

Category:

AdminPanel

Target version:

Candidate for patchlevel

Start date:

2012-02-23

Due date:

% Done:

Estimated time:

TYPO3 Version:

4.5

PHP Version:

Tags:

Complexity:

Is Regression:

Sprint Focus:

Description

With activated caching framework the function extGetNumberOfCachedPages in class.t3lib_tsfebeuserauth.php provokes an allocate memory error when there are (too) many cache entries for a page.

It happens while the function "getByTag" of the variableFrontend unserializes the cache entries and puts them into the array, just to count themn later to display the number of cache entries in the admin panel.

Related issues 1 (0 open — 1 closed)

Related to TYPO3 Core - Story #81460: Sacrifice caches' ill conceived getIdentifiersByTag

Closed

2017-06-03

Actions

Issue # Delay: days Cancel

History
Notes
Property changes

Actions

Copy link

Updated by Stefan Galinski about 12 years ago

I have added Christian as watcher to this issue. Maybe he has some ideas how to fix that issue. If you can find a solution yourself in the meanwhile, feel free to open a new review request. :-)

http://wiki.typo3.org/Contribution_Walkthrough_Tutorials

Actions

Copy link

Updated by Leon Dietsch about 12 years ago

My quick fix is to comment the part out and return "0" :)
I don't think the number of cache entries for the current page is relevant in the admin panel. I suggest to remove the feature. Another possibility would be to add functions in the caching frontends and backends for counting the number of cache entries for a cache. But as long as only the admin panel needs to count the entries, I'd prefer to remove it.
I'd be glad to open a review request with the necessary changes, after the soultions (or better solutions than mine) have been discussed.

Actions

Copy link

Updated by Stefan Galinski about 12 years ago

Status changed from New to Needs Feedback

Just set this to "Needs Feedback", because it needs discussion like you said. I can't help myself, because I simply don't know any specifics about the caching framework.

Actions

Copy link