Leaving https://weather.com/weather/hourbyhour/l/92677:4:US open for a while causes OS-level crash
Reported by
strom...@gmail.com,
Dec 27
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/71.0.3578.80 Chrome/71.0.3578.80 Safari/537.36 Steps to reproduce the problem: 1. Just browse to https://weather.com/weather/hourbyhour/l/92677:4:US 2. Leave it open for hours or days 3. The computer gets very, very slow. 4. If you don't kill the tab in time, the whole OS must be rebooted to restore functionality. What is the expected behavior? Display the page, long-term, without causing a system crash. What went wrong? It's a mad dash to close the tab before things get too-far-gone. I'm inculcating the habit of not leaving this URL open long, though it's one of few URL's I do this for. It'd help a lot if top and/or ps could show what URL each chromium-browser process is displaying. Then I could alt-f1 to a virtual console and kill the offending chromium in a top, instead of killing random chromium processes until I hit the right one. The GUI itself (cinnamon) is frequently too unresponsive to allow me to kill the offending chromium through the GUI. Did this work before? N/A Chrome version: 71.0.3578.80 Channel: n/a OS Version: Mint 19 Tara Flash Version: Memory leak? Cryptocurrency miner? Not sure.
,
Dec 31
Tried testing the issue on the reported chromium version #71.0.3578.80 using Ubuntu 17.10 by following below steps. Steps: ====== 1.Launched chrome. 2.Naviagted to "https://weather.com/weather/hourbyhour/l/92677:4:US". 3.Left the computer by keeping the above URL open for approximately 4hours. 4.Observed that the page is still displayed and the system did not crash. @reporter: Could you please review the above procedure followed and let us know if anything being missed here. Requesting you to provide the crash id by navigating to "chrome://crashes" and also confirm if the issue is specific to Mint 19 Tara. Thanks.!
,
Jan 15
Closing issue due to lack of information provided. If the issue still exists please open a new issue with the reproduction steps. |
|||
►
Sign in to add a comment |
|||
Comment 1 by viswa.karala@chromium.org
, Dec 28