Posts by jurialmunkey

Quote from mglae

Are there other reports for Python 3.11 too? E.g. with Fedora 37 or Archlinux?

More detailed research in LE requires using a debug image.

There's been reports for Android but not so much other Linux.

EDIT: Just had someone report same issue on Ubuntu 22, so not limited to LibreELEC. Reported the issue on xbmc github since the issue seems to be platform agnostic: https://github.com/xbmc/xbmc/issues/22344

However, it seems to occur more frequently on ARM chipsets and not so much on x64, which would explain fewer reports on "normal" distros. Running Generic-Legacy LibreELEC in a VirtualBox VM on my laptop (Intel i7) I've been able to make the issue occur twice but it seems relatively difficult compared to the reports I'm getting from ARM users.

I've got a couple of users who can reliably reproduce the issue on ARM devices as soon as we enable the API which parses XML data via ElementTree. See specifically this comment (first issue was addressed but second one is the ElementTree issue) https://github.com/jurialmunkey/p…ment-1364672534

And here's the two crash logs from my VM with backtrace showing elementtree thread segfaulting.

hastebin

hastebin

Quote from mglae

SEGFAULT due to null pointer access in elementtree, no idea about the cause:

Code

Thread 1 (Thread 0x7f1654ff96c0 (LWP 151486)):
#0  0x0000000000000000 in ?? ()
#1  0x00007f169188738e in ?? () from /usr/lib/python3.11/lib-dynload/_elementtree.so
#2  0x00007f16b9a6f781 in ?? () from /usr/lib/libpython3.11.so.1.0
#3  0x00007f16b9a18c1b in _PyObject_MakeTpCall () from /usr/lib/libpython3.11.so.1.0
#4  0x00007f16b99c8c94 in _PyEval_EvalFrameDefault () from /usr/lib/libpython3.11.so.1.0
#5  0x00007f16b9ae72e0 in ?? () from /usr/lib/libpython3.11.so.1.0
#6  0x00007f16b9ae7383 in PyEval_EvalCode () from /usr/lib/libpython3.11.so.1.0
#7  0x00007f16b9b259f3 in ?? () from /usr/lib/libpython3.11.so.1.0
#8  0x00007f16b9b25bf6 in ?? () from /usr/lib/libpython3.11.so.1.0
#9  0x00007f16b9b25cd0 in ?? () from /usr/lib/libpython3.11.so.1.0
#10 0x00007f16b9b28dec in PyRun_FileExFlags () from /usr/lib/libpython3.11.so.1.0
#11 0x0000000000ab8810 in CPythonInvoker::executeScript(_IO_FILE*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, _object*) ()
#12 0x0000000000acb2f0 in CPythonInvoker::execute(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::vector<std::__cxx11::basic_string<wchar_t, std::char_traits<wchar_t>, std::allocator<wchar_t> >, std::allocator<std::__cxx11::basic_string<wchar_t, std::char_traits<wchar_t>, std::allocator<wchar_t> > > >&) ()
#13 0x0000000000acbeca in CPythonInvoker::execute(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::vector<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > > const&) ()
#14 0x00000000015211be in CLanguageInvokerThread::Process() ()
#15 0x0000000000e559a3 in CThread::Action() ()
#16 0x00000000016a2b93 in ?? ()
#17 0x0000000000e53d93 in ?? ()
#18 0x00007f16b6f2a403 in ?? () from /usr/lib/libstdc++.so.6
#19 0x00007f16b70f0460 in ?? () from /usr/lib/libc.so.6
#20 0x00007f16b7169a2c in ?? () from /usr/lib/libc.so.6

Display More

Experiencing the same issue with TMDbHelper and a couple of my other addons using ElementTree. Wondering if this will be fixed or if we will need to wait on an upstream fix in Python?

If waiting on an upstream fix, I can tell ELEC users how to disable those features. Not really an ideal approach though considering ET is part of the Python standard library and is particularly useful in the context of Kodi due to skinning being XML based.