Description: Hello, On pc Debian x86-64 with master sources updated today, I got a crash when trying to open About dialog with SKIA Steps to Reproduce: 1. Launch console/term 2. export SAL_USE_VCLPLUGIN=gen && export SAL_FORCESKIA=1 && ./soffice.bin 3. Menu Help/About Actual Results: Crash Expected Results: No crash Reproducible: Always User Profile Reset: Yes Additional Info: I can also reproduce this with SAL_FORCESKIA=0 but I don't reproduce this if I unset SAL_FORCESKIA
Created attachment 164920 [details] bt with debug symbols
Please attach your /proc/cpuinfo and config.log (from build dir).
Created attachment 164924 [details] cpuinfo
Created attachment 164925 [details] config.log
Please run this in Valgrind and attach the log ("VALGRIND=memcheck soffice"). Also, why do you use soffice.bin directly instead of the wrapper script? And why do you force Skia instead of just enabling it?
(In reply to Luboš Luňák from comment #5) > Please run this in Valgrind and attach the log ("VALGRIND=memcheck soffice"). Ok, I gonna update my second local repo (where there are symbols but no enable-dbgutil) + run "make clean && make". I'll provide a Valgrind trace afterwards. > Also, why do you use soffice.bin directly instead of the wrapper script? I just used Miklos' suggestion from http://document-foundation-mail-archive.969070.n3.nabble.com/How-to-enable-Skia-on-Linux-tt4286424.html#a4286466 I don't know the diff between soffice and soffice.bin > And why do you force Skia instead of just enabling it? since by default SKIA wasn't enabled. It's not the case for me, that's why I had created http://document-foundation-mail-archive.969070.n3.nabble.com/How-to-enable-Skia-on-Linux-tt4286424.html#a4286466 thread and saw SAL_FORCESKIA option from Miklos's feedback.
Created attachment 165031 [details] Valgrind trace
Created attachment 165032 [details] Valgrind trace 2 Here's a second Valgrind trace after a crash when just did this: ./soffice --norestore --valgrind >& /tmp/valgrind2.log (BTW, I still need SAL_USE_VCLPLUGIN=gen and export SAL_FORCESKIA=1 without them, LO doesn't use SKIA)
Luboš Luňák committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/7d0e9168daba1411c15315a4d5f481ed1e5dc356 fix offsets in our SSSE3 Skia functions (tdf#136326) It will be available in 7.1.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Luboš Luňák committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/fddbf05d5b9b83863c1bf85e5c9821d87671768e initialize possible CPU intrinsics use also for normal Skia (tdf#136326) It will be available in 7.1.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
On pc Debian x86-64 with master sources updated today, I don't reproduce this. I can see I use SKIA/Vulkan after export SAL_USE_VCLPLUGIN=gen && export SAL_FORCESKIA=1 Thank you Luboš! (remark: I did a "make postprocess" and removed user profile, I still need to also use "SAL_FORCESKIA=1" to enable Skia).
@Luboš Luňák, do the patches need to be backported to libreoffice-7-0 ?
(In reply to Xisco Faulí from comment #12) > @Luboš Luňák, do the patches need to be backported to libreoffice-7-0 ? No, this is only master.