0

crashing chrome tab when browsing github (macos)

Jason fa 6 anys updated by Ionuț Botizan fa 6 anys 3

I've only been seeing the crashes on GitHub, but I haven't confirmed that it's anything particular about GitHub that causes the crashes


I made a screen recording of the browser crashing instantly when I enable Window Resizer


https://youtu.be/ZvlBbqxG_kI

Answer

Answer

I guys,

Sorry for the late response... At the time this ticket was created I could reproduce the bug but I didn't have time to perform an in-depth investigation. All I know is that it manifested itself when the option to automatically display the resize info on all pages, which meant a little piece of code was injected in every page and it somehow interfered with the Github code...

Unfortunately, now that I had a bit of spare time, I couldn't reproduce it anymore. Maybe Github changed something on their end or it's because I now have Chrome v.69 and back then I had v.68... Not really sure...

Please let me know if the problem persists for you.

Best Regards,

Ionuț

+1
Under review

Hi Jason,


Thanks for reporting this and taking the time to make a video about it! Most people would usually just remove the extension and move on... :)

I'll look into it this weekend.


Best Regards,

Ionuț

+1

I have been having this issue for a while too but never really got time to find out until today. Tried disable/enable all my extension and found the culprit. Gona disable this extension until it's fixed since accessing github is essential to me on daily basis.

Answer

I guys,

Sorry for the late response... At the time this ticket was created I could reproduce the bug but I didn't have time to perform an in-depth investigation. All I know is that it manifested itself when the option to automatically display the resize info on all pages, which meant a little piece of code was injected in every page and it somehow interfered with the Github code...

Unfortunately, now that I had a bit of spare time, I couldn't reproduce it anymore. Maybe Github changed something on their end or it's because I now have Chrome v.69 and back then I had v.68... Not really sure...

Please let me know if the problem persists for you.

Best Regards,

Ionuț