Closed totaam closed 9 years ago
@onlyjob: which debian release is this? which version of webp? How did you install?
The webp decoding is the cause of the crash it seems (you can confirm by specifying all encodings except webp in
encodings
):#5 0x00007fffdf2863da in __pyx_pf_4xpra_6codecs_4webp_6decode_6decompress (__pyx_v_data=<optimized out>, __pyx_v_has_alpha=<optimized out>, __pyx_v_rgb_format=<optimized out>, __pyx_self=<optimized out>) at xpra/codecs/webp/decode.c:1890
I don't think there were any changes in this codec for quite some time (trac says at least 8 months: [/browser/xpra/tags/v0.14.x/src/xpra/codecs/webp]), so maybe it is a library issue.
It is Debian Jessie; Xpra installed from unreleased package. libwebp (0.4.1-1.2). Xpra crashes right away when started with
--encoding=webp
. How can I specify list of allowed encodings in commine line? Thanks.
libwebp (0.4.1-1.2) [[BR]] FWIW: latest stable libwebp from their 0.4 branch is 0.4.3. [[BR]] We don't have any problems with webp on osx, win32, Fedora, centos,.. (and none reported against the Debian / Ubuntu packages for that matter) [[BR]]
How can I specify list of allowed encodings in commine line? Thanks.
--encodings=
ie:xpra attach --no-mmap --encodings=png,rgb
Shows on the server:
using png as primary encoding, also available: rgb24
Another easy way to confirm, is to only use
webp
or use it as primary encoding:--encoding=webp
.
It is a library change... I've built Xpra-0.4.18 in the exactly the same environment where I built 0.14.23 and reproduced the issue. By comparing build logs I see that libwebp was upgraded from 0.4.1-1.2 to 0.4.3-1 in the build environment... I was however running Xpra with webp 0.4.1-1.2... I'll check whether libwebp should generate tighter dependency or if they introduced regression...
I'm closing this as invalid as this doesn't look like this has anything to do with our code. Let us know if there are ways we are supposed to be detecting these sorts of ABI change at runtime. (we have access to the
WebPGetDecoderVersion
which we expose via xpra info)
Thanks for your help. I confirm it is breakage in libwebp-0.4.3 that I reported in
Issue migrated from trac ticket # 848
component: client | priority: major | resolution: invalid
2015-04-29 08:51:37: onlyjob created the issue