We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Pesquisar no apoio

Evite burlas no apoio. Nunca iremos solicitar que telefone ou envie uma mensagem de texto para um número de telefone ou que partilhe informações pessoais. Por favor, reporte atividades suspeitas utilizando a opção "Reportar abuso".

Saber mais

MozCrashReason: MOZ_CRASH() EXCEPTION_BREAKPOINT

  • 6 respostas
  • 2 têm este problema
  • 2 visualizações
  • Última resposta por 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

Todas as respostas (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:

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.

Modificado por TyDraniu a

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.