Bug#1072299: Compositor-related crashes

2025-01-19 Thread Daniel Richard G.
All right, I've figured out what was going on, as well as a fix. Going back to that backtrace I posted some months ago, which I've seen crop up again and again: #0 0x00... in partition_alloc::internal::OnNoMemoryInternal(unsigned long) () #1 0x00... in partition_alloc::TerminateBecause

Bug#1072299: Compositor-related crashes

2024-07-12 Thread Andres Salomon
On 7/12/24 03:34, Daniel Richard G. wrote: I did another round of debugging, and have some new findings to report. To start with, I put a breakpoint on OnNoMemoryInternal(). That works better than trying to catch the SIGILL. However, this failure mode has been relatively infrequent with my modif

Bug#1072299: Compositor-related crashes

2024-07-12 Thread Daniel Richard G.
I did another round of debugging, and have some new findings to report. To start with, I put a breakpoint on OnNoMemoryInternal(). That works better than trying to catch the SIGILL. However, this failure mode has been relatively infrequent with my modified 126.0.6478.126 build. More common lately

Bug#1072299: Compositor-related crashes

2024-07-06 Thread Daniel Richard G.
On Tue, 2024 Jun 25 14:26-04:00, Andres Salomon wrote: > > That backtrace makes sense; it's running OnNoMemoryInternal(), which > calls PA_IMMEDIATE_CRASH(), which generates an invalid opcode customized > for various architectures (ironically to provide a better backtrace > compared to calling a

Bug#1072299: Compositor-related crashes

2024-06-25 Thread Andres Salomon
On 6/25/24 00:23, Daniel Richard G. wrote: On Thu, 2024 Jun 13 15:07-04:00, Andres Salomon wrote: Oops, sorry, I didn't see this email. Let me finish getting v126 out the door, and then circle back if the crash is still present there. I still see the problem with .114, alas. Tabs crash, somet

Bug#1072299: Compositor-related crashes

2024-06-03 Thread Daniel Richard G.
I'm going to need a spot of help with this. I have Chromium running under GDB, with surprisingly low overhead (I can browse like normal if I drop the --single-process flag). As far as I could find, the "trap invalid opcode" error reported in syslog is synonymous with a SIGILL, so I set "handle SIG

Bug#1072299: Compositor-related crashes

2024-05-31 Thread Daniel Richard G.
On Fri, 2024 May 31 21:49-04:00, Andres Salomon wrote: > Oh! Apparently my info is outdated. According to > , this was fixed back in August. It does > indeed look like > > has the dbgsym

Bug#1072299: Compositor-related crashes

2024-05-31 Thread Andres Salomon
On 5/31/24 18:59, Daniel Richard G. wrote: On Fri, 2024 May 31 18:36-04:00, Andres Salomon wrote: I'm going from memory here, but I believe the dak installation on security.debian.org doesn't keep dbgsym packages for historical reasons. Thus, they're only available once chromium gets moved to s

Bug#1072299: Compositor-related crashes

2024-05-31 Thread Daniel Richard G.
On Fri, 2024 May 31 18:36-04:00, Andres Salomon wrote: > > I'm going from memory here, but I believe the dak installation on > security.debian.org doesn't keep dbgsym packages for historical reasons. > Thus, they're only available once chromium gets moved to > stable-proposed-updates. https://tr

Bug#1072299: Compositor-related crashes

2024-05-31 Thread Andres Salomon
On 5/31/24 15:51, Daniel Richard G. wrote: I believe I've found a correlation: The crashes seem to have started with an instance of firefox-esr (115.11.0esr-1~deb12u1) that I was running on the side, since earlier today. Once I closed Firefox, the crashiness went away, completely. (This is on th

Bug#1072299: Compositor-related crashes

2024-05-31 Thread Daniel Richard G.
Sigh, spoke too soon. Chromium still crashes in both modes (tab and browser) even without Firefox running, but much less frequently. I had a good half-hour without crashes after closing Firefox, enough to lead me to think that was the cause. At this point, we're probably better off waiting to see

Bug#1072299: Compositor-related crashes

2024-05-31 Thread Daniel Richard G.
I believe I've found a correlation: The crashes seem to have started with an instance of firefox-esr (115.11.0esr-1~deb12u1) that I was running on the side, since earlier today. Once I closed Firefox, the crashiness went away, completely. (This is on the same laptop that needs --use-gl=egl to avoi

Bug#1072299: Compositor-related crashes

2024-05-31 Thread Andres Salomon
On 5/31/24 14:48, Daniel Richard G. wrote: Package: chromium Version: 125.0.6422.112-1~deb12u1 Severity: important Recently, I have been observing crashes of individual tabs, and even of the entire browser, when navigating some Web pages. The crashed tabs correlate with the following syslog mess

Bug#1072299: Compositor-related crashes

2024-05-31 Thread Daniel Richard G.
Package: chromium Version: 125.0.6422.112-1~deb12u1 Severity: important Recently, I have been observing crashes of individual tabs, and even of the entire browser, when navigating some Web pages. The crashed tabs correlate with the following syslog messages (multiple instances listed below): 2024