PySide6 6.2.0 does not run & crash

Dariusz

Hey

I'm a bit lost. I've been stuck at PySide6.0 since its release, I'm unable to push any newer version as it always crashes in release mode and debugs.
Process finished with exit code -1073740791 (0xC0000409)
Any ideas how to bite it? Feels like dlls are missing somehow.

Win10x64
PyCharm
PySide6 6.2.0

Regards
Dariusz

SGaist

Hi,

Which version of Python are you using ?
How do you install Qt ?
Which Python environment manager do you use ?

Dariusz

Hey
Python 3.7.4
Pycharm packet manager, I pick 6.2.0 version.
Python Environment manager...mmm I don't think I do? Or at least knowingly do, pycharm handles it.

TIA!

I've run tests all day long, now trying vers starting from 6.0.1 and going up each ver 1 by 1. But 6.2.0 has like 25% change of starting, else it crashes.

SGaist

Do you have that issue with a minimal script ?
Did you try to check with a different version of Python like 3.8 or 3.9 ?

Dariusz

@SGaist said in PySide6 6.2.0 does not run & crash:

Do you have that issue with a minimal script ?
Did you try to check with a different version of Python like 3.8 or 3.9 ?

Minimal script runs, I did not try different pythons yet.
Ver 6.0.1 crashes too :- (
Im literally adding print (x) to each line of code 1 by 1 trying to track down the cause of it. It crashes at random prints. Which is bananas. I rolled back to 6.0.0 everything works.

I'll try installing fresh environment, see if that can fix it...

Dariusz

Ok I tried fresh venv, python 3.9 and 6.2.0. Still crash. Simple app works, my app crashes somewhere in Qt as whenever I run debug or release in Pycharm I end up with the same result. just error code. No breakpoint/etc.

When ever I manage to run it & try to do something, I tend to get error with QTreeView

QTreeView
self.view.update()
TypeError: historyView.update() takes exactly one argument (0 given)

This in Qt 6.0.0 worked fine. To push update of QTreeView.

SGaist

You should not need to call update yourself.

But argument number error is strange...

Try calling it passing the geometry of your widget as parameter.

Dariusz

@SGaist Yep fixed thos, and all other ones. Looks like API change, sadly still crash with vague code.

SGaist

I would say it's rather a binding issue, update is a parameter less slot. You should be able to use it.

You should check the bug report system to see if it's something known and if not open a ticket.

Dariusz

@SGaist Yea its strange... I just went line by line debuging the entire start sequence of script. It started. I restart without line by line debugging and it crashes.

The odd thing that I find is that QAbstractItemView.update() does need an index passed to it. Which is fine, but what strikes me odd is that Shiboken is imported from Shiboken and not from Shiboken6?
I though PySide6 & Shiboken6 were meant to be now 6?
This is from Library >

# imports
import PySide6.QtCore as __PySide6_QtCore
import PySide6.QtGui as __PySide6_QtGui
import Shiboken as __Shiboken

SGaist

Where do you have that shiboken import ?

Dariusz

@SGaist

# encoding: utf-8
# module PySide6.QtWidgets
# from S:\pythoNenvs\venv39_01\lib\site-packages\PySide6\QtWidgets.pyd
# by generator 1.147
# no doc

# imports
import PySide6.QtCore as __PySide6_QtCore
import PySide6.QtGui as __PySide6_QtGui
import Shiboken as __Shiboken

Its generated by Pycharm down in Python_stubs

SGaist

I am as surprised as you.

I do not see the use for it especially for user code.

eyllanesc

@Dariusz try execute on cmd: python main.py and show the complete error message.