1523567 - I canceled a Firefox session due to memory leaks. On restart, Crash Report window appears. CLICK RESTORE SESSION, and that crashed.

Status: RESOLVED INCOMPLETE

(Firefox :: Session Restore, defect, P3)

Description

[SES]

Attachment: Firefox session crash RPT info for events on jan 28 & 29, 2019.

I canceled a Firefox session due to memory leaks. On restart, Crash Report window appears. CLICK RESTORE SESSION, and that crashed. Action repeated, and likely repeated (for all tabs?).

Zero tabs were successfully restored.

I could not actually tell if there were different tabs affected, since with each crash report, Clicking RESTORE SESSION, just produced another crash report.

There should be something like 30 of these crash reports, as I assumed that different reports might actually be for different tabs, and there were est. more than 20 tabs.

I'm really screwed, as IE is terrible and slow, plus FF is my preferred browser.

My signed in Vista session ID is SANFORD, to tie back to my ~30 crash reports.

eMAIL ID = mailto:[e-mail]

Comment 1

[SES]

FF is up to date.
Vista is up to date also.

Comment 2

[Liz Henry (:lizzard) (relman/hg->git project)]

Hi, I'm sorry about the crashes.
Can you check about:crashes, follow the link from one of the relevant crashes, and paste the url in here? That may help us find a cause. Thanks!

Comment 3

[SES]

I don't know if my crash/bug report here (id=1523567) was accurate enough for your staff or not, so I am going to re-state the crash scenario:

1. FF response slowing down as increasing memory used,

2. I used TASK MANAGER to END PROCESS of all FF tasks (I have been doing this for 12-15 years, and as many as 1-4 times per day),

3. I restarted FF,

4. FF prompted with RESTORE SESSION and a little CHECK BOX that I had never seen before, that was already checked, IIRC.

5. It wasn't clear what the check box was going to accomplish, so I unchecked it, and clicked RESTORE SESSION.

6. The result was a FF CRASH REPORT window.

7. I selected/allowed a crash report to be sent and clicked on RESTART SESSION,

8. This resulted in a repeat of (6 & 7) above.

9. Not knowing if the crash report was going to occur once per tab, I repeated #7 over and over again in the (vain) hope that if performed once per tab, I might eventually get a successful FF session restart/restore. But that was to no avail.

10. So I gave up on FF ever running again.

---

Just now I tried starting FF, for the first time since:

---

Submitted Crash Reports
Report ID Date Submitted
bp-ca896db6-b4aa-48cc-aead-33b140190130 1/30/2019, 12:38 AM

https://crash-stats.mozilla.com/report/index/bp-ca896db6-b4aa-48cc-aead-33b140190130

AND IT STARTED UP IN THE NORMAL FASHION, WITH THE "RESTORE SESSIONS" OPTION, and it worked as normal!

I would note, that since 30 Jan., I have not done a single thing to affect the execution of FF. Nothing. So why it started working last night, 04 February 2019, 7 PM, is a mystery to me!

Comment 4

[Liz Henry (:lizzard) (relman/hg->git project)]

Interesting. Mike, does this sounds like some kind of profile issue? What do you think?
Not sure we are going to be able to replicate this, but maybe the crash report has some clues.

Comment 5

[John Thompson]

Hi all,
Don't know whether this is the right thread, but since upgrading to Ffx 65.0 every time I quit the browser, the application window closes but then there's a lot of CPU usage and eventually a crash report dialogue box popps up. This does not happen when I just close a tab, only when I quit completely.
I just upgraded to 65.0.1 in the hope that you'd seen and fixed the problem but it persists.
You'll be receiving a lot of crash reports if my (very standard) case is anything to go by.
Windows 10.0.17134.523

Comment 6

[John Thompson]

(In reply to John Thompson from comment #5)

Count me out on this one, it turned out to be this:
https://support.mozilla.org/en-US/questions/1249036

Deleting offline website data as per Philipp's instructions solved the problem I was experiencing.

Comment 7

[Mike de Boer [:mikedeboer]]

Well, yeah it does sound that this is a corrupted profile, somehow. It'd be somewhat interesting to see if clearing 'offline website data' as mentioned in comment 6 and choosing 'Restore Previous Session' after that would make it work.

Other than that I'm flying blind at this point and the crash reports aren't telling an awful lot here, unfortunately.

Comment 8

[Mike de Boer [:mikedeboer]]

Oh and this may not at all be session restore related! Even though it might be the trigger, it's quite likely that some webapp was behaving badly - since SES is talking about memory leaks making Fx unusable - and that restoring the app just makes the problem return.

Comment 9

[Mike de Boer [:mikedeboer]]

Closing due to inactivity > 1yr.