https://bugs.kde.org/show_bug.cgi?id=488653
--- Comment #19 from eseif...@error-reports.org --- (In reply to Fabian Vogt from comment #18) > FWICT it's memory corruption, maybe caused by libtaskmanager or its > integration into pbi. > > Valgrind could help here, but unfortunately it's not quite straightforward > to wrap the host executable. Try this: > > cd $(mktemp -d) > cp /usr/bin/plasma-browser-integration-host . > cat >pbi-wrap.sh <<EOF > #!/bin/sh > exec valgrind --log-file="$PWD/vg.log" > "$PWD/plasma-browser-integration-host" "\$@" > EOF > chmod a+x pbi-wrap.sh > sed "s#/usr/bin/plasma-browser-integration-host#$PWD/pbi-wrap.sh#" > /usr/lib64/mozilla/native-messaging-hosts/org.kde.plasma.browser_integration. > json >json > sudo mount --bind json > /usr/lib64/mozilla/native-messaging-hosts/org.kde.plasma.browser_integration. > json > > Substitute the correct path for the extension .json for your browser. > > Then start the browser and somehow reproduce the crash, it should be visible > in the temporary directory's vg.log file Thanks a lot! Unfortunately, with this wrapper plasma-browser-integration-host always fails to start on my system. This is most likely due to missing support for AVX-512 instructions in valgrind (bug #383010). I will have a look how I can work around this. -- You are receiving this mail because: You are watching all bug changes.
