Bug 251656 - x11-servers/xorg-server segmentation fault running chrome devtools
Summary: x11-servers/xorg-server segmentation fault running chrome devtools
Status: Open
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-x11 (Nobody)
URL:
Keywords: crash, needs-qa
Depends on:
Blocks:
 
Reported: 2020-12-07 00:49 UTC by dave
Modified: 2020-12-09 09:07 UTC (History)
3 users (show)

See Also:
fernape: maintainer-feedback? (x11)


Attachments
Xorg.0.log (22.44 KB, text/plain)
2020-12-07 00:49 UTC, dave
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description dave 2020-12-07 00:49:10 UTC
Created attachment 220334 [details]
Xorg.0.log

This segfault is repeatable (at the moment). Everytime I try to go into chromium devtools, this happens:

[  1264.602] (EE) Backtrace:
[  1264.604] (EE) 0: /usr/local/bin/Xorg (?+0x0) [0x41cb00]
[  1264.605] (EE) 1: /lib/libthr.so.3 (?+0x0) [0x80083fb60]
[  1264.606] (EE) 2: /lib/libthr.so.3 (?+0x0) [0x80083f0c0]
[  1264.608] (EE) 3: ? (?+0x0) [0x7fffffffe003]
[  1264.609] (EE) 4: /lib/libc.so.7 (?+0x0) [0x800a126d0]
[  1264.609] (EE) 
[  1264.609] (EE) Segmentation fault at address 0xe082c8000
...
[  1264.609] (EE) 
[  1271.654] (WW) NVIDIA(0): WAIT (2-S, 17, 0x1b14, 0x0000b6a4, 0x0000ba10)
[  1278.654] (WW) NVIDIA(0): WAIT (1-S, 17, 0x1b14, 0x0000b6a4, 0x0000ba10)
[  1281.655] (WW) NVIDIA(0): WAIT (2-S, 17, 0x1a98, 0x0000b6a4, 0x0000ba44)
[  1288.655] (WW) NVIDIA(0): WAIT (1-S, 17, 0x1a98, 0x0000b6a4, 0x0000ba44)

After this occurs, the screen goes off. The X server is found (via remote SSH) to be running at 100% CPU trying to yield(). The (WW) lines at the end seem to indicate the server is waiting on the card in my likely naive analysis. 

A complete Xorg.log is attached. I am using branches/2020Q3 as my ports tree. Note that this segfault only occurred after I upgraded to 12.2, previously 11.2 ran just fine. This bug also occurs using both the old binaries (built against 11.2) and the new binaries (built against 12.2)...yes as a matter of fact I -did- rebuild everything against 12.2. :D

Thanks in advance.