Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Instagram crashes on firefox

  • 9 uphendule
  • 1 inale nkinga
  • 30 views
  • Igcine ukuphendulwa ngu FredMcD

more options

Instagram crashes on firefox every few days, happens when reading posts or watching stories (no new content is loading during crash). Happens only on firefox, never on other websites. Happen every few days, when I press reload the website after crash, it works temporarily, but it may happen after some days. My network is good enough.

using 91.0 (64bit) firefox, macOS Big Sur 11.5.1, both latest version

tried delete cookies and history, turn off hardware acceleration. I didn't install any extra extensions.

feel angry everytime crash, didn't manage to submit crash report, just do it now, not sure how it could help though

https://crash-stats.mozilla.org/report/index/a2005fd4-b2b7-4a01-b23d-aa5620210813 https://crash-stats.mozilla.org/report/index/4bcc784f-60a1-443d-8eae-2e7390210813 https://crash-stats.mozilla.org/report/index/9e2a3f31-43c9-4121-9d4e-1786b0210813 https://crash-stats.mozilla.org/report/index/373d5c78-66fc-4fbb-937b-d81780210813

feel sad because i know it would crash again after some days. What can I do?

All Replies (9)

more options

A crash report could tell us what happen to cause the crash. Or sometimes where to look.


bp-Product Firefox Release Channel release Version 90.0.2 Build ID 20210721174149 (2021-07-21) Buildhub data OS macOS 11 OS Version 11.5.1 20G80

bp-a2005fd4-b2b7-4a01-b23d-aa5620210813 bp-4bcc784f-60a1-443d-8eae-2e7390210813 bp-9e2a3f31-43c9-4121-9d4e-1786b0210813 bp-373d5c78-66fc-4fbb-937b-d81780210813

Signature: nsThreadPool::Run

MOZ_CRASH Reason (Sanitized) : MOZ_RELEASE_ASSERT(r == 60)

Crash Reason EXC_BAD_ACCESS / KERN_INVALID_ADDRESS

This is for Sumo's Related Bugs 1487833 REOPENED --- Crash in nsThreadPool::Run

Helpful?

more options

What were you doing at the time? surfing, watching a clip, reading something . . . . The bug report was looking at the player.

Helpful?

more options

FredMcD said

A crash report could tell us what happen to cause the crash. Or sometimes where to look. bp-Product Firefox Release Channel release Version 90.0.2 Build ID 20210721174149 (2021-07-21) Buildhub data OS macOS 11 OS Version 11.5.1 20G80 bp-a2005fd4-b2b7-4a01-b23d-aa5620210813 bp-4bcc784f-60a1-443d-8eae-2e7390210813 bp-9e2a3f31-43c9-4121-9d4e-1786b0210813 bp-373d5c78-66fc-4fbb-937b-d81780210813 Signature: nsThreadPool::Run MOZ_CRASH Reason (Sanitized) : MOZ_RELEASE_ASSERT(r == 60) Crash Reason EXC_BAD_ACCESS / KERN_INVALID_ADDRESS This is for Sumo's Related Bugs 1487833 REOPENED --- Crash in nsThreadPool::Run

what can I do for this Sumo's related bugs?

Helpful?

more options

FredMcD said

What were you doing at the time? surfing, watching a clip, reading something . . . . The bug report was looking at the player.

3times when I crash, I am just browsing instagram posts(not necessarily happen when I load new posts, I am just reading posts I already load. when I read them, they crash. But if I restart the crash website and read the same post, it didn't crash, but it will happen after few days.). 1time it is when I watch a story (video), then it crashes!

Helpful?

more options

The bug reports are for the Sumos among us as the bug gets very technical.


Many site issues can be caused by corrupt cookies or cache.

Warning ! ! This will log you out of sites you're logged in to. You may also lose any settings for that website.

If there is still a problem,

Start Firefox using Troubleshoot(Safe) Mode {web link}

A small dialog should appear. Click Start In Troubleshoot(Safe) Mode (not Refresh). Is the problem still there?

While you are in Troubleshoot(Safe) mode;

Try disabling graphics hardware acceleration in Firefox. Since this feature was added to Firefox it has gradually improved but there are still a few glitches.

How to disable Hardware Acceleration {web link}

Helpful?

more options

FredMcD said

The bug reports are for the Sumos among us as the bug gets very technical. Many site issues can be caused by corrupt cookies or cache. Warning ! ! This will log you out of sites you're logged in to. You may also lose any settings for that website. If there is still a problem, Start Firefox using Troubleshoot(Safe) Mode {web link} A small dialog should appear. Click Start In Troubleshoot(Safe) Mode (not Refresh). Is the problem still there? While you are in Troubleshoot(Safe) mode; Try disabling graphics hardware acceleration in Firefox. Since this feature was added to Firefox it has gradually improved but there are still a few glitches. How to disable Hardware Acceleration {web link}

actually after my second last crash, i turn off hardware acceleration, it doesn't help after my last crash, i clear all cookies and cache, not sure if it helps, because normally crash happen after every few random days. I haven't cleared it for 8months, now firefox forgets my preferences and it takes time. But I fear I am just sit and do nothing, and waiting for next crash.

also not sure if trouble shoot works, i have no extensions. and everytime after it crash, after i restore the page it looks normal, so hard for trouble shoot because it happens randomly, and not so often.

Helpful?

more options

If you get another crash, be sure to post its number here.

https://support.mozilla.org/en-US/kb/diagnose-firefox-issues-using-troubleshoot-mode

Safe Mode is a troubleshooting mode that temporarily turns off hardware acceleration, resets some settings, and disables add-ons (extensions and themes), any userChrome.css/userContent.css files, and some other advanced features to help you assess whether these are causing the problem. If the problem goes away, that tells us one thing. If it does not, that tells us something else.

Helpful?

more options

FredMcD said

If you get another crash, be sure to post its number here. https://support.mozilla.org/en-US/kb/diagnose-firefox-issues-using-troubleshoot-mode Safe Mode is a troubleshooting mode that temporarily turns off hardware acceleration, resets some settings, and disables add-ons (extensions and themes), any userChrome.css/userContent.css files, and some other advanced features to help you assess whether these are causing the problem. If the problem goes away, that tells us one thing. If it does not, that tells us something else.

Dear,

I am the original poster, I forgot my account, so I need a new one to talk. Thanks for your help so far ><

Since my last crash, I have cleared my cache and all history, plus everytime I use instagram web, I turn troubleshot mode on. So far, there is no crashes YET. It's been about 10days. I think I need probably 20more days, to convince myself, that the crash problem is solved.

But, occasionally, my IG web doesn't work well. Sometimes it loads slow, for example images can't be loaded, there is a message 'waiting for fbcdn' (something like that) on the lower part of the web page. This problem only exists when browsing IG, or facebook. When those images can't be loaded, sometimes it shows a message 'this image may contain a person, or something...', those images are white, and black words with message appear on it.

Sometimes, after I finishing browsing posts and stories, I try to turn to my own profile. When I try to process, it can't. I am stuck, I know it doesn't work well. Something likes loading happens, but it can't finalise. Well, thats fine. But usually IG remembers if you already read those stories. But if this happen (can't process after finish reading normally), IG won't remember I already read those stories, it's a bit annoying. Sometimes I suspect my network isn't quite that good? But this problem only happens on fb/ig.

This monday, after I browse IG for about 30minutes, after I finish I find my battery drop drastically, I lose about 15% battery during it, plus my computer is hot, looks like burnt. I turn on activity monitor on my mac, but I misread %GPU to check my firefox is the cause. I should read %CPU to see if its number go crazy. I will do properly next time it happens.

All this sucks, probably it is acceptable. But the main problem is, sometimes when you f5, or you kill the browser and re-enter, instagram will change the pecking order of unread posts (it thinks I quit ig because I didn't read the first posts properly, but actually it is because I can't load it). It triggers me, because I want to watch some posts first, their order matters. And it is not fair to me, because I visit this website to have fun, I don't know why I have to suffer! It is not fair.

I already update firefox to latest version. I don't know what can I do!

Helpful?

more options

I called for more help.

Helpful?

Buza umbuzo

Kufanele ulogele ukungena ku-akhawunti yakho ukuze uphendule amaphosti. Uyacelwauqale umbuzo omusha, uma ungekabi nayo i-akhawunti namanje.