Details
-
Bug
-
Resolution: Incomplete
-
Not Evaluated
-
None
-
5.15.2
-
None
-
Ubuntu 18.04
Linux DEN-UI 5.4.0-71-generic #79~18.04.1-Ubuntu SMP Thu Mar 25 05:45:39 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
Python 3.6.8
Description
Running a 100% python code GUI using PySide2, we receive the following memory errors and PySide2 does not error out gracefully. We just get a SIGABRT. The error messages are not always the same.
corrupted size vs. prev_size
Process finished with exit code 134 (interrupted by signal 6: SIGABRT)
"Memory chunk control structure fields in the adjacent following chunk are being overwritten due to out-of-bounds access by the code." Source: https://stackoverflow.com/questions/49628615/understanding-corrupted-size-vs-prev-size-glibc-error
Another symptom:
OpenType support missing for "Ubuntu", script 14 OpenType support missing for "Ubuntu", script 9 OpenType support missing for "Ubuntu", script 17 OpenType support missing for "Ubuntu", script 11 OpenType support missing for "Ubuntu", script 12 OpenType support missing for "Ubuntu", script 16 OpenType support missing for "Ubuntu", script 13 OpenType support missing for "Ubuntu", script 32 OpenType support missing for "Ubuntu", script 20 OpenType support missing for "Ubuntu", script 19 OpenType support missing for "Ubuntu", script 15 free(): invalid pointer Process finished with exit code 134 (interrupted by signal 6: SIGABRT)
Similar PySide bugs found (although old):
https://bugreports.qt.io/browse/PYSIDE-135
Our requirements.txt
aenum==2.2.6 cycler==0.10.0 et-xmlfile==1.0.1 kiwisolver==1.3.1 matplotlib==3.3.3 numpy==1.19.5 openpyxl==3.0.7 pandas==1.1.5 Pillow==8.1.0 pkg-resources==0.0.0 pyparsing==2.4.7 PySide2==5.15.2 python-can==3.3.4 python-dateutil==2.8.1 pytz==2021.1 rope==0.18.0 shiboken2==5.15.2 six==1.15.0 wrapt==1.12.1