Browser task gets stuck after a view refresh / reload #602
Comments
VIEWSION
changed the title
|
This sounds like a syntax issue on the page that's causing CodeKit to not be able to remove old stylesheet And, of course, verify that there are no syntax issues on the page. |
|
Ok - I check this out. I also noticed that it is much better when the Chrome cache is activated. I usually deactivate caching for development. When the problem occurs, there is not only a high memory usage in the activity monitor but also a very high CPU load on the chrome task. |
|
here is the screenshot. Seems that the injected stylesheets do not get deleted somehow... I also wanted to make a copy of the whole source, but when I tried to open the source window it was reloading and all the css links disappeared.
|
|
Yep. That explains it. Do you see any JavaScript console errors logged in the web inspector?
|
|
No - there are no JS error logs |
|
In that case, I'll need the project so I can test it on my end. Zip it and send me a download link, please. Sent from my iPhone
|
|
Ok. This is not that easy as the setup is quite complex with server side stuff, database and CMS framework... I try to strip it down to a static html demo... |
I use Chrome and Safari on a Mac for preview with browser refreshing. I also use an external server (MAMP). It works fine as expected at the beginning. But after a view (let's say 10-20) reloads, the browser tab gets kind of stuck and it takes a long time until it is responding in any way. I need to close the tab then and open a new one to get it work as expected again.
If I look at the tab task in the activity monitor, I noticed that the memory usage grows on every refresh from about 50MB in the beginning exponentially up to 2GB and more until the task gets completely stuck like described.
The text was updated successfully, but these errors were encountered: