1529178 - firefox crash runs long time

Status: RESOLVED INCOMPLETE

(Firefox :: PDF Viewer, defect, P3)

Description

[zw]

Attachment: catchint3.png

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:65.0) Gecko/20100101 Firefox/65.0

Steps to reproduce:

I open many pages and pdf file, when I leave office, I close many pages except pdf file. This continued for many days, memory goes up, maybe some memory leak occured. I close the firefox, it crashed.

Actual results:

My windows's debug tools will catch these problems. It looks like some problems occured in the "xul.dll"

Expected results:

It should not be occured

Comment 1

[zw]

Attachment: bug.png

Comment 2

[Damira Akh]

Thank you for reporting this issue.

I am leaving some windows and pdf files open today but seems like this testing needs more time.

For now, I placing this Firefox: General, please feel free to correct it.

Comment 3

[Matthew N. [:MattN]]

Did the crash reporter appear? If so, can you load about:crashes and provide a crash ID?

Comment 4

[zw]

I lost that crash report, because my windows debugging tool catch the crash, then bugcather of firefox can't catch the crash.
I also open the about:crashes, there are so many crashes, but the contents of crashes are all same, I think this problem is also same too. crash ID is cdbd9985-7935-4295-85dd-2ca600190301

Comment 5

[Andrew Overholt [:overholt]]

(In reply to zw from comment #4)

I lost that crash report, because my windows debugging tool catch the crash, then bugcather of firefox can't catch the crash.
I also open the about:crashes, there are so many crashes, but the contents of crashes are all same, I think this problem is also same too. crash ID is cdbd9985-7935-4295-85dd-2ca600190301

Thanks! https://crash-stats.mozilla.com/report/index/cdbd9985-7935-4295-85dd-2ca600190301

Comment 6

[Andrew Overholt [:overholt]]

The crash report from comment 5 looks like it's probably just an OOM crash.

Given the specific mention of PDFs here, I'll move this to pdf.js. Oh, and I'll needinfo dmajor since there are the screenshots of a Windows debugging tool and I don't know if they're useful or not :)

Comment 7

[(Away)]

If this happens again and if you are able to guess when the memory is dangerously high but hasn't yet crashed, it may be helpful to get a report from about:memory.

Comment 8

[zw]

Sorry everyone, I can't reproduce this problem. If I reproduce it again, I will submit new reports

Comment 9

[zw]

Suddenly, I get crash. Unfortunately, the crash reports differ from that one.

https://crash-stats.mozilla.org/report/index/e271b78f-91a2-42b3-964f-eb90f0190419

Comment 10

[BugBot [:suhaib / :marco/ :calixte]]

The priority flag is not set for this bug.
:bdahl, could you have a look please?

For more information, please visit auto_nag documentation.

Comment 11

[Calixte Denizet (:calixte)]

There is nothing actionable here: no pdf, crash reports don't exist anymore.