You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a freshly installed Orange3 version 3.29.3 using Miniconda (conda 4.10.3). I'm using two monitor setup with integrated graphics from CPU. I have a somewhat unique situation with my Orange installation, it will always crash if I open it on my secondary monitor but it works properly if I open it on my primary monitor.
What's wrong?
Orange will always crash when I open some widget, for example Corpus Viewer or Line Chart. When I open those two widget when Orange is in my secondary monitor, Orange will crash. But if I open those widget while Orange is at my primary monitor, it works perfectly.
How can we reproduce the problem?
Reproducing the crashing:
Plug a secondary monitor to your PC and set it to Extend mode
Start orange using terminal orange-canvas in the second monitor (Orange has to be started in the second monitor for this crash to happen)
Add Corpus Viewer or Line Chart to the workspace and open it
The widget window will open with blank content and then crash.
The above situation will not happen if you use Duplicate mode with your secondary monitor.
What's your environment?
Operating system: Windows 10 21H1 Build 19043.1110
Orange version: 3.39.3
How you installed Orange: Using Miniconda conda install -c conda-forge orange3==3.93.3
Extra context
I run some checks using memory dump and find out the following result. After some digging using the keyword NtUserGetHDevName (symbol name from memory dump) I stumbled upon this thread on Prusa repo (prusa3d/PrusaSlicer#2142). In the thread they have the same problem with two monitor and Nahimic drivers. I use two monitor and Nahimic driver, but I confirmed the problem is not with Nahimic driver (I tested it by disabling the service and uninstalling the driver).
To summarize, this might be a problem with Qt working on two monitor and probably not Nahimic driver.
fahminlb33
changed the title
Orange3 version 3.29.3 crashes when using two monitor setup
Orange3 version 3.29.3 crashes when using two monitor in Extend mode
Aug 1, 2021
Thanks for the in-depth report. Could you perhaps check which qt version do you have there? Look at pyqt and qt entries of conda list.
If you are willing to experiment - what happens if you try to use some other version of Qt? With conda-forge, you are most likely getting 5.12 (this is the same one we distribute in our official Windows packages).
Testing with Qt 5.15 would be ideal, but this may be difficult because official conda(-forge) packages past 5.12 do not exist yet.
Unfortunately after I upgraded PyQt5 using pip to version 5.15.2 Orange could not be started with the following error:
Warning: QT_DEVICE_PIXEL_RATIO is deprecated. Instead use:
QT_AUTO_SCREEN_SCALE_FACTOR to enable platform plugin controlled per-screen factors.
QT_SCREEN_SCALE_FACTORS to set per-screen DPI.
QT_SCALE_FACTOR to set the application global scale factor.
QWidget: Must construct a QApplication before a QWidget
I have a freshly installed Orange3 version 3.29.3 using Miniconda (conda 4.10.3). I'm using two monitor setup with integrated graphics from CPU. I have a somewhat unique situation with my Orange installation, it will always crash if I open it on my secondary monitor but it works properly if I open it on my primary monitor.
What's wrong?
Orange will always crash when I open some widget, for example Corpus Viewer or Line Chart. When I open those two widget when Orange is in my secondary monitor, Orange will crash. But if I open those widget while Orange is at my primary monitor, it works perfectly.
How can we reproduce the problem?
Reproducing the crashing:
orange-canvas
in the second monitor (Orange has to be started in the second monitor for this crash to happen)The above situation will not happen if you use Duplicate mode with your secondary monitor.
What's your environment?
conda install -c conda-forge orange3==3.93.3
Extra context
I run some checks using memory dump and find out the following result. After some digging using the keyword
NtUserGetHDevName
(symbol name from memory dump) I stumbled upon this thread on Prusa repo (prusa3d/PrusaSlicer#2142). In the thread they have the same problem with two monitor and Nahimic drivers. I use two monitor and Nahimic driver, but I confirmed the problem is not with Nahimic driver (I tested it by disabling the service and uninstalling the driver).To summarize, this might be a problem with Qt working on two monitor and probably not Nahimic driver.
The text was updated successfully, but these errors were encountered: