FS#63945 - [mesa] causes FATAL:memory_linux.cc Out of Memory crash when starting Chromium.
Attached to Project:
Arch Linux
Opened by Matthew Sexton (wsdmatty) - Sunday, 29 September 2019, 04:06 GMT
Last edited by Toolybird (Toolybird) - Friday, 26 May 2023, 05:59 GMT
Opened by Matthew Sexton (wsdmatty) - Sunday, 29 September 2019, 04:06 GMT
Last edited by Toolybird (Toolybird) - Friday, 26 May 2023, 05:59 GMT
|
Details
Description:
After upgrading to testing version 19.2.0-1 of Mesa, Chromium crashes before opening the browser window. [1537:1537:0928/232202.066810:FATAL:memory_linux.cc(42)] Out of memory. [1722:1722:0928/232202.661766:FATAL:memory_linux.cc(42)] Out of memory. [1746:1746:0928/232203.111063:FATAL:memory_linux.cc(42)] Out of memory. [1755:1755:0928/232203.539134:ERROR:gpu_channel_manager.cc(397)] ContextResult::kFatalFailure: Failed to create shared context for virtualization. I have a core dump of the process, but it's basically useless. I'm currently in the process of building chromium and mesa with debug symbols to get a usable backtrace. Once that's done I'll add the backtrace and possibly file a bug report upstream. Here is the current backtrace which shows nothing. Additional info: * package version(s) * config and/or log files etc. * link to upstream bug report, if any Steps to reproduce: |
This task depends upon
Closed by Toolybird (Toolybird)
Friday, 26 May 2023, 05:59 GMT
Reason for closing: Fixed
Additional comments about closing: This looks old and stale..so assuming fixed. If not, please report upstream.
Friday, 26 May 2023, 05:59 GMT
Reason for closing: Fixed
Additional comments about closing: This looks old and stale..so assuming fixed. If not, please report upstream.
https://gitlab.freedesktop.org/mesa/mesa/issues/1860
Also: i don't think this version of Mesa should've been pushed to testing. According to https://www.mesa3d.org/relnotes/19.2.0.html 19.2.0 is a development release, not a stable release. The next stable release will be 19.2.1.
kernel: traps: chromium[6084] trap invalid opcode ip:55c6c4a32acf sp:7ffdf5864d20 error:0 in chromium[55c6c1784000+6f5b000]