Bug #75782
closed
Massive performace problems in backend during work
0%
Description
I'm using Opera 36.x to work with the backend. But Chrome 50.x has the same problems.
In the beginning everything in the backend works smooth and fast. But after a few minutes (e.g. 10 - 15 min) of intensive work (new content, translation, edit content) everything get worse. You have to wait seconds to press a button, write in an input field. Sometimes the tab crashes.
The only workaround is to press Strg-F5, when the speed slows down. After pressing Strg-F5 you can work a few minutes with full speed, then the backend will slow down again.
Updated by Mathias Schreiber almost 9 years ago
- Status changed from New to Needs Feedback
- Assignee set to Mathias Schreiber
Can you measure whether the problem starts on the server or the clientbrowser?
Given the amount of information it's a bit hard to tell what might be going on.
You could hop in on Slack so we can have a chat and find out whats going on.
Updated by Mario Wilhelm almost 9 years ago
I don't think it is a server-side problem.
My colleagues have the the same problems on different servers with different Typo3 installations.
I have installed Slack, where to go?
Updated by Mathias Schreiber almost 9 years ago
Just head over here to create an account.
https://forger.typo3.org/slack
You can then ping me directly.
Updated by Alexander Opitz over 8 years ago
Was this issue discussed and resolved?
Updated by Mario Wilhelm over 8 years ago
It was discussed, but not resolved, because Mathias Schreiber used a Mac and could not confirm this problem. It seems to be a Windows + Chrome only problem.
Updated by Alexander Opitz over 8 years ago
I think you mean Windows + Chrome on client side?
But I think there will be more user with such a setup but no reports from them. hmmmm
Maybe you can try the Chrome Developer Tools to look if this are rendering or JavaScript issues.
Updated by Mario Wilhelm over 8 years ago
Yes, Windows + Chrome on Client-Side.
I think, that the RTE is the cause of this problem. Maybe a memory problem with RTE and Chrome/Win.
In our company we all have this problem (Win7/Chrome, Win10/Chrome/Opera). Firefox seems to be OK.
Updated by Christoph Werner about 8 years ago
- PHP Version changed from 5.6 to 7.0
Hi all!
I´ve got a similar problem with Firefox and Chrome in Windows 7. Chrome can cope it a bit better, so it takes more time before recognizing that its getting slow.
When I monitor the ram-usage I see it rising and rising. When working for about one hour, it could be 1 GB or more (only for ff or chrome!).
Best,
Chris
Updated by Alexander Opitz about 8 years ago
- PHP Version changed from 7.0 to 5.6
Updated by Raphael Zschorsch almost 8 years ago
I work with a Mac and have this problem with Chrome as well on different servers, etc. So not only a Win/Chrome problem imo.
Updated by Mona Muzaffar over 7 years ago
- Status changed from Needs Feedback to New
Updated by Riccardo De Contardi about 7 years ago
- Status changed from New to Needs Feedback
If I have understood it correctly, the symptom of this issue is an exponential growth of the memory used. Could it be reproduced on version 8.7?
RTEHtmlarea has been removed from core
Updated by Mario Wilhelm about 7 years ago
I would say yes, but not so fast as in 7. It takes longer till the effect happens, but it happens.
Updated by Riccardo De Contardi about 7 years ago
- Category changed from Backend User Interface to Performance
- Status changed from Needs Feedback to New
Updated by Riccardo De Contardi about 7 years ago
- Assignee deleted (
Mathias Schreiber)
Updated by Sybille Peters almost 7 years ago
I can't reproduce this, however I don't have a Windows system available.
I am wondering why not more people are affected by this.
If you still can reproduce, can you do any of the following:
- can you reproduce this on a fresh TYPO3 install without additional extensions and configuration changes?
- can you give more information about your setup (e.g. additional browser plugins etc.)
Also, it looks like there are a number of tools for analyzing memory leaks, taking snapshots etc. for chromium, so could you do one of the following:
- analyze it yourself using these tools
or
- create snapshots that might help in analyzing it for you
This problem sounds very annoying and I am hoping we can do something about it.
There are a number of help pages for Chromium that assist in analyzing / taking snapshots, e.g.
Updated by Benni Mack almost 6 years ago
- Status changed from New to Needs Feedback
Hey everybody,
can somebody shed some light on this, if it is HTMLarea related? If so, we'd need to address this for v8 in https://github.com/FriendsOfTYPO3/rtehtmlarea as v7+HTMLarea is not supported anymore (only ELTS, thus, it'd need a ticket there).
Updated by Benni Mack almost 5 years ago
- Status changed from Needs Feedback to Closed
Closing this due to lack of feedback.