My app keeps crashing and i've never used the Debugger befor!

[mrjj]

Hi
It's hard to guess at, but maybe the rt is null and hence it crashes asking for ->d

In the call stack, it seems to be inside Qt
but if you scroll to the button some of your code should be shown

Such crashes normally comes from openGl issues.

Can you run any of the QML or openGl examples that comes with Creator ?

[Kris Revi]

@mrjj but if you scroll to the button some of your code should be shown
im confused here :P button?

[mrjj]

@Kris-Revi
sorry fat fingers. :)
To the bottom. The scrollbar can be dragged more down to see the start of the call stack.

[Kris Revi]

This?

[mrjj]

@Kris-Revi
Yes but it didnt show anything interesting.
Do you call FullScreen any where ?
seems to start there.

Also, does other examples work ?
Could be openGL setup that is messed up.

[Kris Revi]

@mrjj weird hmmm so i found the bit of code that was the cause!

    const QScreen* screen = qApp->primaryScreen();
    w.setGeometry( QRect(QPoint(0,0), screen->geometry().size()) );
    w.setWindowFlag(Qt::MaximizeUsingFullscreenGeometryHint,true);

    w.showFullScreen();

but when i now run my App it's loading and "running" but no window comes up :S

[mrjj]

@Kris-Revi
Did you remove the fullscreen or how did you make it run ?

Try with
w.show()

[Kris Revi]

@mrjj so i added w.show(); and ran the debugger again and got this

[mrjj]

@Kris-Revi

Ok so it is when it tries to show the render surface.

You have to try some of the openGl examples and see.

I guess its your openGL since it seems to crash on showing.

https://doc.qt.io/qt-5/qtopengl-hellogl2-example.html

They are available directly in creator.

[Kris Revi]

@mrjj so i just ran that example and it worked without problems

[Kris Revi]

@mrjj i just noticed this

QQuickWidget is only supported on OpenGL. Use QQuickWindow::setGraphicsApi() to override the default.

could this be it?

[mrjj]

@Kris-Revi

Hi
yes it could very well as normally Desktop is using openGl and mobile some other ES? but
normally it's automatic.

This is a Desktop pc windows right ?

Did you compile Qt your self ?

Maybe its a Qt6 thing. try setting it to openGl via the setGraphicsApi as it says and then see.

[Kris Revi]

@mrjj yea it's for desktop now :) 6.2.0 but im compiling for both Android and Desktop in same project! and wanted to test the App on the Desktop

[mrjj]

@Kris-Revi

Can it be that on startup some other API is set ?
Or you added some defines to .pro so it thinks its Android ?

[Kris Revi]

@mrjj so the App works perfectly with QQuickWindow::setGraphicsApi(QSGRendererInterface::OpenGL); weird why i would need to set that tho :S hmmm

[Kris Revi]

@mrjj question in the pro file can't i do this

win32
{
    CONFIG(release, debug|release): LIBS += -LC:\QMsgPack\bin -lqmsgpack
    INCLUDEPATH += C:\QMsgPack\bin
    DEPENDPATH += C:\QMsgPack\bin
}

win32
{
    CONFIG(debug, debug|release): LIBS += -LC:\QMsgPack\bin -lqmsgpack
    INCLUDEPATH += C:\QMsgPack\bin
    DEPENDPATH += C:\QMsgPack\bin
}
unix
{
    contains(ANDROID_TARGET_ARCH,arm64-v8a)
    {
        ANDROID_PACKAGE_SOURCE_DIR = \
           $$PWD/android

        ANDROID_EXTRA_LIBS = \
            $$PWD/android/libs/libqmsgpack_arm64-v8a.so
    }
    LIBS += -L$$PWD/android/libs/ -lqmsgpack_arm64-v8a

    INCLUDEPATH += $$PWD/android/libs
    DEPENDPATH += $$PWD/android/libs
}

? :S

[mrjj]

@Kris-Revi
Yes that seems perfect. should not interfere with which backend is used.

I cant tell either. Did you use any new Qt6 things ?
Could be fun to see if it does the same say in 5.12

[Kris Revi]

@mrjj for some reason with the code above it does this

i've selected the Desktop but it is trying to find the "arm / android" version :S