This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

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

MozCrashReason: MOZ_CRASH() EXCEPTION_BREAKPOINT

  • 6 replies
  • 2 have this problem
  • 2 views
  • Last reply by cor-el

more options

New computer Firefox crash report MozCrashReason: MOZ_CRASH() https://crash-stats.mozilla.com/report/index/e775c995-d75a-4b6d-b19f-10cee1170512

installed ram available 15.9 GB 31 % reserved for individual processes 1% CPU used

New computer Firefox crash report MozCrashReason: MOZ_CRASH() https://crash-stats.mozilla.com/report/index/e775c995-d75a-4b6d-b19f-10cee1170512 installed ram available 15.9 GB 31 % reserved for individual processes 1% CPU used

All Replies (6)

more options

That is an OOM (out-of-memory) crash report where not enough free contiguous memory is available.

  • SystemMemoryUsePercentage: 46
  • OOMAllocationSize: 65536
  • Available Virtual Memory: 169,107,456 bytes (161.27 MB)

Maybe try to disable this Kaspersky extension that shows in the crash report:

  • light_plugin_F6F079488B53499DB99380A7E11A93F6@kaspersky.com

Start Firefox in Safe Mode to check if one of the extensions ("3-bar" menu button or Tools -> Add-ons -> Extensions) or if hardware acceleration is causing the problem.

more options
more options

Your memory is quite fragmentated. Firefox is unable to allocate another block of this size.

Try to install 64-bit Firefox, maybe it helps.

Modified by TyDraniu

more options

Memory has 0% fragmentation. What part of crash report indicated fragmentation? new reports : bp-0a62504e-71da-469b-bb94-b13611170518

bp-b027d77b-8540-490a-809a-d9f981170515

bp-9e32b22f-775d-4371-9b0a-de2ad1170514 bp-29308bd6-c8c5-4e17-86a2-f23740170513 bp-036f8912-7dcf-4b2f-9b8c-aa09c1170513

more options

rflexible said

What part of crash report indicated fragmentation?

Its name: OOM small.


Address space fragmentation is a big issue in 32-bit Firefox. For users running a 32-bit Firefox on 32-bit Windows there's only 2GB of usable address space available. For users running 32-bit Firefox on 64-bit Windows there's 4GB of usable address space, but fragmentation is still an issue. And you ending with 10% of it; it has to be fragmented.

more options

https://crash-stats.mozilla.com/report/index/0a62504e-71da-469b-bb94-b13611170518 Total Virtual Memory 4,294,836,224 bytes (4 GB) Available Virtual Memory 401,408,000 bytes (382.81 MB) Available Physical Memory 8,707,788,800 bytes (8.11 GB)

System Memory Use Percentage 48 OOM Allocation Size 2 bytes (this is weird)

Looks that "Available Virtual Memory" is that low data can no longer be swapped to the pagefile and thus even a 2 bytes allocation is failing.