Mozilla 도움말 검색

고객 지원 사기를 피하세요. 저희는 여러분께 절대로 전화를 걸거나 문자를 보내거나 개인 정보를 공유하도록 요청하지 않습니다. "악용 사례 신고"옵션을 사용하여 의심스러운 활동을 신고해 주세요.

Learn More

Firefox constantly crashes certain websites on startup

more options

When I try to visit certain websites on Firefox, they crash no matter what, even after reloading the page. This still happens in Troubleshoot mode, and even after doing a clean reinstall of Firefox it still happens. Here are some of the recent crash IDs:

bp-58277bb5-edfc-47aa-b940-664980230818 bp-d25f54be-20c8-4931-aa26-bbfba0230818 bp-89a4cf72-0ff3-4f80-9476-6a0110230818 bp-61a579db-f6b8-4f9c-8bc0-05c010230818 bp-e58e4646-d571-4885-8c4f-24af60230818 bp-416a9731-bfe8-4aa0-abc9-b77b00230818 bp-ae207202-7b30-4ac6-a98e-c19770230818

I don't know if I should include all of them because there is a lot.

When I try to visit certain websites on Firefox, they crash no matter what, even after reloading the page. This still happens in Troubleshoot mode, and even after doing a clean reinstall of Firefox it still happens. Here are some of the recent crash IDs: bp-58277bb5-edfc-47aa-b940-664980230818 bp-d25f54be-20c8-4931-aa26-bbfba0230818 bp-89a4cf72-0ff3-4f80-9476-6a0110230818 bp-61a579db-f6b8-4f9c-8bc0-05c010230818 bp-e58e4646-d571-4885-8c4f-24af60230818 bp-416a9731-bfe8-4aa0-abc9-b77b00230818 bp-ae207202-7b30-4ac6-a98e-c19770230818 I don't know if I should include all of them because there is a lot.

모든 댓글 (1)

more options

Sorry to hear about the crashes and thank you for the report IDs. One thing you could try right now is to update Firefox to version 116.0.3 and see whether that makes any difference. See: Update Firefox to the latest release.

Some of these reports are very similar to one another, which might indicate a pattern. Forum volunteers do not have access to the site URLs, so I can't tell whether the crash signatures are correlated with specific sites or whether any of them might happen on a particular site.

js::jit::ICStub::isFallback - 3 reports from Monday, August 14th

"jit" stands for Just in Time, which is a reference to one of the JavaScript compilers. The JavaScript compilers are disabled in Troubleshoot Mode, so this particular pattern would be avoided in that situation. The crash is caused by a read violation, which I think means that Firefox tried to access memory that doesn't belong to it and got slapped down by Windows.

One possible reason for this to happen would be a bug in Firefox that was triggered accidentally by a script on the site, but another possibility is that the site is trying to exploit a flaw in the browser to attack the browser. Do you consider it to be a trustworthy site?

I don't have any actionable advice on working around this crash, unless there is a way to filter more of the site's scripts using uBlock Origin or similar extension.

JSScript::getScope - 1 report from Monday, August 14th

This appears to be a crash in the JavaScript interpreter rather than the compiler. The crash reason is indicated as:

MOZ_RELEASE_ASSERT(idx < storage_.size())

This means, I think, that Firefox detected a fatal condition that led it to shut down to protect against doing something invalid. But I have no idea exactly what was going wrong.

I don't have any actionable advice on this one, either.

nsTArray_Impl<T>::AppendElementsInternal<T> | nsTSubstring<T>::~nsTSubstring | mozilla::MediaResult::~MediaResult - 1 report from Tuesday, August 15th

This crash occurred in a function related to decoding an MP4. But I can't tell why this MP4 was a problem when others don't crash Firefox. ??

If you notice any particular problems with videos on certain sites, perhaps there is something about their encoding that is different.

je_malloc - 2 reports from Monday, August 14th

This crash occurred when Firefox was allocating memory and Windows reported an access violation. I can't tell what the cause was, but the reports reference processing some style rules, and mention animation.

This appears to be less common than the other crash signatures and I don't know of a way to work around it.


As a general thought, could you check for any graphics driver updates? See: Upgrade your graphics drivers to use hardware acceleration and WebGL.