1

(Problem reported to Apple Jul 5, 2019 but I got no answer as of Aug 1, 2019)

If you work for Apple please review FB6505912. I have sent to you system reports and Samples from the process.

I am experiencing a very strange bug on Safari. If I leave a webpage that uses websockets heavily, then sleep the system and turn it on back after a couple of minutes, the tab page keeps the CPU at 99.9% all the time, burning down my battery and CPU (it reaches 100ÂșC). I need to open Activity monitor and kill the page every single day.

This is happening to two websites, firebase.com and g1.com.br.

enter image description here

My system is running MacOS 10.14.6 (18G84) and Safari 12.1.2 (14607.3.9).

It's a MBP 15' i7 2018 with 32Gb of RAM.

I have already cleared the NVRAM and SMC and it didn't solve my problem. I think it's a bug from Safari itself.

Thank you, it's my first post here so let me know if you need more information.

  • 2
    We are not Apple, nor in any way related to them, so besides hoping to draw attention to the problem, what exactly is your question here? – nohillside Aug 1 '19 at 10:17
  • Yes I know you guys are not Apple, but if someone that works for then see this post, please read my report there. They are totally ignoring my reports. I am reporting here because I hope to find someone experiencing the same and or know the solution for this problem. – Pedro Paulo Amorim Aug 1 '19 at 10:48
  • Is this some custom code you are running or just the website as is? – nohillside Aug 1 '19 at 11:10
  • 1
    Firstly, welcome to Ask Different! :) I hope you come to find this site a valuable resource! As for your question, I wouldn't assume that Apple is ignoring your report. If it's been escalated to engineering and you were told to expect a call back, I'd just follow up again to get an update. While it can be very frustrating from a user's perspective, the engineering guys can get extremely overwhelmed at times - especially in the months leading up to new operating system releases. – Monomeeth Aug 1 '19 at 11:23
  • I didn't get any feedback, I did send three reports already in different days. :/ Thank you for the answer! – Pedro Paulo Amorim Aug 1 '19 at 11:25
1

As troubleshooting steps, I'd try the following:

  • Test with another browser to see what happens. If the problem isn't repeated then you're starting to isolate the issue, although I would then try a 3rd browser for good measure to see how it also behaves.
  • Boot into Safe Mode (see below) and test again with Safari

Boot into Safe Mode

Follow these steps to boot your MBP into Safe Mode:

  1. Fully shut down your Mac
  2. Restart your Mac
  3. Immediately press the Shift key and keep it down
  4. Let go of the Shift key when you see the login window (NOTE: If you have FileVault enabled you may need to log in twice).
  5. Take a note of what happens (i.e. visit the sites again with Safari and try to replicate the problem)
  6. Exit Safe Mode by restarting your Mac as normal
  7. Test again when booted normally

Let me know how these steps went and we'll go from there.

|improve this answer|||||

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .