Поиск в Поддержке

Избегайте мошенников, выдающих себя за службу поддержки. Мы никогда не попросим вас позвонить, отправить текстовое сообщение или поделиться личной информацией. Сообщайте о подозрительной активности, используя функцию «Пожаловаться».

Learn More

Regular crashes started recently - Bug 1706429

  • 5 ответов
  • 1 имеет эту проблему
  • 2 просмотра
  • Последний ответ от hugh.gibson

more options

I've been getting a lot of crashes on a website I'm developing - for example bp-b1597aaa-c596-4641-ad9b-a9dea0210503 . It's at the stage now where every time I open the site (or a clone of it) it crashes.

This appears to be reported at https://bugzilla.mozilla.org/show_bug.cgi?id=1706429 but has severity and priority of P3, perhaps based on 39 reports when the ticket was raised. But there are now 614 of them: https://crash-stats.mozilla.org/signature/?product=Firefox&signature=js%3A%3Afrontend%3A%3AGeneralParser%3CT%3E%3A%3AprimaryExpr&date=%3E%3D2021-04-27T17%3A01%3A00.000Z&date=%3C2021-05-04T17%3A01%3A00.000Z&_columns=date&_columns=product&_columns=version&_columns=build_id&_columns=platform&_columns=reason&_columns=address&_columns=install_time&_columns=startup_crash&_sort=-date&page=1#reports

This is really annoying because I'm having to do my website development in Chrome.

I've been getting a lot of crashes on a website I'm developing - for example bp-b1597aaa-c596-4641-ad9b-a9dea0210503 . It's at the stage now where every time I open the site (or a clone of it) it crashes. This appears to be reported at https://bugzilla.mozilla.org/show_bug.cgi?id=1706429 but has severity and priority of P3, perhaps based on 39 reports when the ticket was raised. But there are now 614 of them: https://crash-stats.mozilla.org/signature/?product=Firefox&signature=js%3A%3Afrontend%3A%3AGeneralParser%3CT%3E%3A%3AprimaryExpr&date=%3E%3D2021-04-27T17%3A01%3A00.000Z&date=%3C2021-05-04T17%3A01%3A00.000Z&_columns=date&_columns=product&_columns=version&_columns=build_id&_columns=platform&_columns=reason&_columns=address&_columns=install_time&_columns=startup_crash&_sort=-date&page=1#reports This is really annoying because I'm having to do my website development in Chrome.

Изменено hugh.gibson

Все ответы (5)

more options

bp-b1597aaa-c596-4641-ad9b-a9dea0210503 Signature: js::frontend::GeneralParser<T>::primaryExpr

Uptime 18 seconds

Crash Reason EXCEPTION_ACCESS_VIOLATION_READ

eplgFirefox.dll = ESET

This is for Sumo's Related Bugs 1706429 NEW --- Startup Crash in [@ js::frontend::GeneralParser<T>::primaryExpr]

more options

Update or reinstall ESET.

more options

I've disabled all ESET features which affect the internet and browser with no effect. ESET updated this morning.

The page doesn't work when Firefox is opened in Safe mode or normal mode. However, it's OK in a private browsing window.

I cleared all cookies for the server and it still fails. That implies that it might be a cookie set on another domain e.g. Twitter.

Recent crash in normal mode: bp-d7e7ce23-7ac9-4efd-b36d-91de90210505 Recent crash in safe mode: bp-0197a022-a984-41c3-aa09-80ea30210505

more options

When using Private Window, not all add-ons are active.

The new crash reports are the same as the first one.


It could be the work of one of your add-ons, or it could be Hardware Acceleration. How to disable Hardware Acceleration {web link}

Type about:addons<enter> in the address bar to open your Add-ons Manager. Hot key; <Control> (Mac=<Command>) <Shift> A)

In the Add-ons Manager, on the left, select Extensions. Disable a few add-ons, then Restart Firefox.

Some added toolbar and anti-virus add-ons are known to cause Firefox issues. Disable All Of them.

If the problem continues, disable some more (restarting FF). Continue until the problem is gone. After, you know what group is causing the issue. Re-enable the last group ONE AT A TIME (restarting FF) until the problem returns.

Once you think you found the problem, disable that and re-enable all the others, then restart again. Let us know who the suspect is, detective.

more options

I was running in Safe mode and still getting the crashes. According to the addons manager, all extensions are disabled in Safe mode. I already had hardware acceleration disabled.

I have two slightly different versions of the website that causes the crash, and they are on one server (in different directories). One is OK, the other crashes FF. Clearly the cookies are common between them. However, different third-party scripts may be loaded (e.g. Mailchimp etc).

On the site that was OK I went into browser tools, used the Storage tab to clear all cookies and also some Local Storage items (which appeared to be Google _uetsid etc). Then in Network tab I disabled the cache, then edited the URL to link to the website that causes the crash. It started working OK.

As a Windows app developer in C++ as well as a website developer I would love to set up a scenario for you but it doesn't seem likely now. I'll let you know if it starts crashing again.