Just had a session crash on me, still got the Crash Reporter open. It was a session with a Private Window open, in which I was doing most of my work. Six months, that is,… (閱讀更多)
Just had a session crash on me, still got the Crash Reporter open. It was a session with a Private Window open, in which I was doing most of my work. Six months, that is, of work and reading. I'm aware of the general irretrievability of private browsing sessions, but it seems a good idea to be very certain and exhaust the possibilities before I unpause my meltdown.
Like I said, the Crash Reporter is still open. Looking at it now. With the language suggesting to me that as long as I leave it open, Firefox hasn't quit or restarted in "full", to my understanding—that the session is still extant in some way. With the checkbox 'Include the address of the page I was on' too... Well, the page I was on was in a Private Window all right. Unless there's a loophole not noted in the Reporter that it can't/doesn't retrieve addresses from private browsing, or that it automatically substitutes the last non-private address, etc.... Then this means the information still exists, doesn't it? Crash be damned? Right now, at least as long as the reporter is open... The implication to me is at least that one bit of information is not completely lost. And if that's not lost, then maybe the other pages in the tab aren't lost yet either. Or all the other tabs in the window. Or the copious notes I'd been maintaining in the address bar's history.
Not that I think there's somehow a quick fix/retrieval possible, but if there's anything at all possible here, I'll try and do it. Regardless if it goes far beyond what can managed through Firefox normally. Private Browsing data is stored in memory, right? So if my surmise that the data has not actually been flushed from memory yet is correct, isn't there something radical I can do to freeze or dump the current state of my memory? Maybe the entire state of my system even, such that the data can be analyzed/retrieved at a later time? Whether it requires a technical touch and mastery leaps and bounds above my current literacy, or if it would need to undergo some drawn-out, folding@home-esque process to be decompiled and analyzable... Literally, if something is possible in this situation where I at least think the data still exists and is calling back or accessible to the Firefox application in some form, I need to consider it.
I'm running Windows 10 and Firefox 74 (again, tells you how long it's been since I restared Firefox). Anyone who can potentially assist or help guide me through this little Armageddon, you have no idea how much your help would be appreciated. Conversely, if you know for a fact that the tiny shred of hope I'm clinging to per my conjecture about the Crash Reporter and the current state of my Firefox is wrong... Then fire away, it's a bullet I guess I'll be biting.