White halo on screen periphery, aprox 10-12mm width (at worst/initially), gradient-to-normal oriented toward center of screen.
Occurred 5.23.2020 11:30pm. First occurrence.
Never any other issues other than mildly swollen battery, replaced 2019, known issue on this model.
Macbook Pro (retina, 15-in, mid 2015).
MacOS Mojave 10.14.6.
Scenario: I usually put computer to sleep at nights. I probably shut down 4-5x monthly. So, incident occurred after computer on an running all day. Headphones, power cord, sleeping external HDD all plugged in. Computer went to sleep aprox 11:00pm ; I was screwing around on my phone so I let the computer sleep. 11:30pm I tried to wake the computer ; non-responsive to space bar or track pad (how I usually wake it) ; also non-responsive to capslock key (light no toggling on/off) and trackpad actuators weren’t “clicking”, also power button non-responsive to a “normal” press (~1-2 seconds). Took out all aforementioned plugged-in stuff. Aprox 5 minutes of “Whelp…f*&k” go by. Long press (~5-10s) turns computer back on ; Seems like it was booting from a shutdown state. White halo present throughout boot cycle, and after logged in. Did not attempt any above mentioned fixes (NVRAM reset, safe mode boot, etc), as the white halo seemed to spontaneously start gradually resolving. It is currently 11:58pm and I can’t see any residual white halo.
Just FYI. This computer has been through the ringer. Video editing and processing, lots of streaming, lots of screen open-closings (15-20x/day every weekday). It was used as my clinical computer for dental school (carried around in a backpack for 4 years). It was “dropped” once; it was in my backpack, I was riding my bike, some butt-toucher (Quest Diagnostics…) hit me with his car (slow speed; he was pulling out of a parking lot and clipped my back wheel as I was crossing him on the sidewalk), I wobbled and fell off the bike, broke most of the fall with my hands (it’s fine, not like I need those, not like I’m a dentist or anything…), then rolled onto my backpack. That was 2017 (got the computer 2016) and it has been fine since.