1177086 - Firefox crash [@ OOM | small ]

Status: RESOLVED DUPLICATE of bug 1190258

(Firefox :: Untriaged, defect)

Description

[helpdeskivc]

I have a big problem with my Firefox browser, I don allow me work
every time its crashed, I must close and reopen it

Version 	38.0.5
Build ID 	20150525141253
Crash Reason 	EXCEPTION_BREAKPOINT
Crash Address 	0x735f1aa1

Comment 1

[Bob Clary [:bc] (inactive)]

You shouldn't send private emails to people with information about a bug. It limits the number of people that see the information and doesn't record it in the bug. Please read https://bugzilla.mozilla.org/page.cgi?id=etiquette.html and https://developer.mozilla.org/en-US/docs/Mozilla/QA/Bug_writing_guidelines for more help on how to file a good bug.

That being said bp-dc36d6bd-9b65-4597-8c46-1a42f2150624 is an [@ OOM | small ] crash.

Comment 2

[Daniel Veditz [:dveditz]]

"OOM" means "Out Of Memory". You appear to have more memory available than the size of the allocation that failed, but perhaps Windows rejected the request because some other resource has run out? Getting down to 80Mb memory left doesn't give Windows a lot of headroom to do the things it does. Do you have a lot of other things running on your machine at the same time? do you have a lot of Firefox windows or tabs open?

Comment 3

[Benjamin Smedberg]

System Memory Use Percentage: 97

Although it's weird that there's pagefile still: Available Page File: 1630715904

dmajor, are there any other clues or steps to help with this?

Comment 4

[(Away)]

On a 32-bit operating system, Firefox is only able to use 2GB of memory. It's easy to reach the limit. Using fewer tabs, or closing the browser frequently, may help a little bit.

Comment 5

[Wayne Mery (:wsmwk)]

How many tabs were open?

Comment 6

[User Dderss]

I have this same crash, but on 64-bit (!) FireFox (Nightly 42):

https://crash-stats.mozilla.com/report/index/e9b66bf7-cd6b-4dac-8a48-3f5d42150728

64-bit browser should not have OOM crashes, but it does.

Comment 7

[:Gijs (he/him)]

(In reply to User Dderss from comment #6)
> I have this same crash, but on 64-bit (!) FireFox (Nightly 42):
> 
> https://crash-stats.mozilla.com/report/index/e9b66bf7-cd6b-4dac-8a48-
> 3f5d42150728
> 
> 64-bit browser should not have OOM crashes, but it does.

Benjamin, any idea what's going on here? (I'm sorry if you're not the right person to ask, please feel free to redirect.)

Comment 8

[(Away)]

> > https://crash-stats.mozilla.com/report/index/e9b66bf7-cd6b-4dac-8a48-3f5d42150728
> > 
> > 64-bit browser should not have OOM crashes, but it does.

The system ran out of page file (64-bit won't help with that). The Firefox process was using something like 15 GB of memory. I'm sure the MemShrink team would love to see an about:memory report the next time it goes that high.

Comment 9

[User Dderss]

Yes, this is physical OOM issue.

Since the time of that crash report I have noticed that FireFox nightly became exploding when whatching YouTube videos serially.

Closing watched video and even erasing history of closed tabs does not free occupied memory, it just continues to grow until death.

This was not the case just a week or two ago, but something has happened to Nightly build so in uncertain circumstances it can not release memory any more.

Comment 10

[(Away)]

> Since the time of that crash report I have noticed that FireFox nightly
> became exploding when whatching YouTube videos serially.
> 
> Closing watched video and even erasing history of closed tabs does not free
> occupied memory, it just continues to grow until death.
> 
> This was not the case just a week or two ago, but something has happened to
> Nightly build so in uncertain circumstances it can not release memory any
> more.

Anthony, could your team look into this?

Comment 11

[User Dderss]

Attachment: memory-report.json.gz

Here is memory report from my current session. It is not close to death yet, but FF already occupies close 10 GB, which was not like that at all couple of weeks ago for the pattern of use I have.

Comment 12

[Gian-Carlo Pascutto [:gcp]]

See but 1190530 for a similar report.

Comment 13

[User Dderss]

Attachment: memory-report.json.gz

This is FireFox Nightly 42 session that now grew to 13 GB; soon to die.

Comment 14

[(Away)]

11,027.73 MB (100.0%) -- explicit
├───8,899.40 MB (80.70%) ── heap-unclassified

This is very likely to be the same issue as bug 1190530 and/or bug 1189194.

Comment 15

[User Dderss]

Thanks; it is interesting what exactly has happened to the Nightly code that inflicted such a wide failure that destroyed normal working of several important things.

Comment 16

[TheRave]

Youtube seems to be a good example here. I make nothing as to to write here and memory is growing during youtube is playing. Time for a restart.


1,274.94 MB (100.0%) -- explicit
├────804.20 MB (63.08%) ── heap-unclassified

    0.00 MB ── d3d11-shared-textures
    0.00 MB ── d3d9-shared-texture
    0.00 MB ── d3d9-shared-textures
    0.00 MB ── d3d9-surface-image
    0.00 MB ── gfx-d2d-vram-draw-target
    0.00 MB ── gfx-d2d-vram-source-surface
   10.32 MB ── gfx-surface-win32
    0.00 MB ── gfx-textures
    0.00 MB ── gfx-tiles-waste
          0 ── ghost-windows
    0.00 MB ── gpu-committed
    0.00 MB ── gpu-dedicated
    0.00 MB ── gpu-shared
1,044.41 MB ── heap-allocated
      1,103 ── heap-chunks
    1.00 MB ── heap-chunksize
1,053.40 MB ── heap-committed
1,103.00 MB ── heap-mapped
      0.86% ── heap-overhead-ratio
          1 ── host-object-urls
    2.60 MB ── imagelib-surface-cache-estimated-locked
    6.83 MB ── imagelib-surface-cache-estimated-total
          0 ── imagelib-surface-cache-overflow-count
    1.64 MB ── js-main-runtime-temporary-peak
          0 ── low-commit-space-events
1,345.63 MB ── private
1,092.61 MB ── resident
1,740.01 MB ── vsize
   63.49 MB ── vsize-max-contiguous

Comment 17

[Anthony Jones (:ajones, :kentuckyfriedtakahe, :k17e)]

Is this fixed by bug 1190258?

Comment 18

[TheRave]

Confirmed. It is fixed with todays nightly. Memory consumption is stable during youtube playing.

121.55 MB (21.29%) ── heap-unclassified

    0.00 MB ── canvas-2d-pixels
    0.00 MB ── d3d11-shared-textures
    0.00 MB ── d3d9-shared-texture
    0.00 MB ── d3d9-shared-textures
    0.00 MB ── d3d9-surface-image
    0.00 MB ── gfx-d2d-vram-draw-target
    0.00 MB ── gfx-d2d-vram-source-surface
   20.57 MB ── gfx-surface-win32
    0.00 MB ── gfx-textures
    0.00 MB ── gfx-tiles-waste
          0 ── ghost-windows
    0.00 MB ── gpu-committed
    0.00 MB ── gpu-dedicated
    0.00 MB ── gpu-shared
  354.71 MB ── heap-allocated
        455 ── heap-chunks
    1.00 MB ── heap-chunksize
  361.27 MB ── heap-committed
  455.00 MB ── heap-mapped
      1.85% ── heap-overhead-ratio
          2 ── host-object-urls
    2.74 MB ── imagelib-surface-cache-estimated-locked
    3.00 MB ── imagelib-surface-cache-estimated-total
          0 ── imagelib-surface-cache-overflow-count
    1.65 MB ── js-main-runtime-temporary-peak
          0 ── low-commit-space-events
  677.30 MB ── private
  613.07 MB ── resident
1,182.67 MB ── vsize
  128.69 MB ── vsize-max-contiguous