'Breakpoint' Crash

[van p]

Screenshot (1020).png

First, I looked in Windows 10 Forums for this. I saw something from 7 years ago that talked about memory leaks, of which I have no knowledge. Then I found something here from last year that mentioned this specific error, but only late/deep into the thread about crashes in general. There was no real resolution that I could see, so here I am.

I assume this message comes from the OS, not the browser; is this correct?

This has happened several times going back several months, and it happens in different browsers, so it's not specifically a Pale Moon thang. It may always happen on my home page (www.ighome.com), but I'm not sure. It turns out to be only a momentary distraction, so I just keep going. If it happens again, I'll try to pay more attention to what's going on. I think sometimes the tabs are recovered and sometimes not. In the meantime, accepting brilliant insights from wherever I can find them.

Edit: Taking a closer look at my screenshot, I see that I was in Cyberfox when this thing displayed with Pale Moon's name attached to it. I may have had both browsers open at the same time; maybe there was some random timing interplay thing going on that resulted in what we see in the screenshot. I vaguely recall that in this instance I got that error in both browsers, one right after the other.

[Moonchild]

It's possible that you simply ran out of system memory. This kind of breakpoint error is a "safe crash" that Pale Moon triggers on purpose if there is an unrecoverable "out of memory" situation. Running out of memory can be caused by any running application at the time of the crash - if Cyberfox gobbled all of it up, it could have crashed Pale Moon due to memory pressure as it ran out of memory itself as well and crashed, for example.

[van p]

Moonchild, thanks for the quick response.

I have 8GB of memory, maybe on the low side by today's standards, I don't know. Neither browser (this time or any other) was being asked to do anything out of the ordinary. I don't know anything about memory use or allocation, but I doubt anything unique was going on there. Still, if this thing is no big deal, I won't worry about it if/when it happens in the future.

Thanks again.

[Nuck-TH]

You could've ran out of virtual memory. Many modern applications(especially CHrome and Electron-based ones) allocate lots of memory with reckless abandon without consideration if they even need it. So if your pagefile is small and physical is moderately used, virtual memory will quickly run out and OOM killer will go out for blood .

[van p]

Thanks, Nuck-TH, for the info. I'd mark this thing solved, but there's no check mark.

[moonbat]

I'd mark this thing solved, but there's no check mark.

I think that feature is only present in the boards that are specifically for tech help - this is the general discussion board.

[Moonchild]

only present in the boards that are specifically for tech help

Correct. It's only there in boards that generally have questions/issues to be answered/solved.