All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 104762] Various segfaults/problems in qt/plasma
Date: Wed, 24 Jan 2018 08:51:33 +0000	[thread overview]
Message-ID: <bug-104762-502@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1783 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=104762

            Bug ID: 104762
           Summary: Various segfaults/problems in qt/plasma
           Product: Mesa
           Version: git
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/Gallium/radeonsi
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: haagch@frickel.club
        QA Contact: dri-devel@lists.freedesktop.org

Created attachment 136931
  --> https://bugs.freedesktop.org/attachment.cgi?id=136931&action=edit
mostly useless gdb backtrace

I think it's related to the series that ended with this commit
"st/glsl_to_tgsi: add ARB_get_program_binary support using TGSI"
https://cgit.freedesktop.org/mesa/mesa/commit/?id=a20016d8277f9cd68620784417a57ae227783a04
but I have to try around a bit more.

It doesn't always happen. I think it's related to the shader cache. Sometimes
deleting the shader cache helps, sometimes it doesn't. I think
MESA_EXTENSION_OVERRIDE=-GL_ARB_get_program_binary helps.

Usually export LD_LIBRARY_PATH=... LIBGL_DRIVERS_PATH=... to another mesa
build, starting the application once and then starting it with the system mesa
again helps. It could be related to mesa first deleting the other shader cache
before making a new one. Some weird race condition?

Applications I've seen affected:
sddm-greeter (segfaulting)
plasmashell (segfaulting
systemsettings (rendering black window content, segfaulting)
krunner (rendering breaking, segfaulting)

As far as I can tell it doesn't happen with mesa debug builds...

More investigation is needed.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 3410 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2018-01-24  8:51 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-24  8:51 bugzilla-daemon [this message]
2018-01-24  9:00 ` [Bug 104762] Various segfaults/problems in qt/plasma bugzilla-daemon
2018-01-24  9:26 ` bugzilla-daemon
2018-01-24 10:33 ` bugzilla-daemon
2018-01-24 14:59 ` bugzilla-daemon
2018-01-25  1:31 ` bugzilla-daemon
2018-01-25  3:59 ` bugzilla-daemon
2018-01-25  8:36 ` bugzilla-daemon
2018-01-25 10:33 ` bugzilla-daemon
2018-01-25 10:56 ` bugzilla-daemon
2018-01-26  0:58 ` bugzilla-daemon
2018-01-26 23:11 ` bugzilla-daemon
2018-01-30  9:25 ` bugzilla-daemon
2018-01-30 10:13 ` bugzilla-daemon
2018-01-31  1:18 ` bugzilla-daemon
2018-02-05  7:07 ` bugzilla-daemon
2018-02-05  8:43 ` bugzilla-daemon
2018-02-05  9:41 ` bugzilla-daemon
2018-02-12  9:00 ` bugzilla-daemon
2018-02-14 22:41 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-104762-502@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.