QML application crashing after update to 5.2.1 and 5.2.2



  • Hello,

    I've tried to update from Qt 5.2.0 to Qt 5.2.1 but my application started crashing on almost every state change. Now I have Qt 5.2.2 from git and the problem is the same, I keep crashing on QV4::FunctionObject::creatScriptFunction almost every time I do some state change. Application runs fine with Qt 5.2.0 (apart from crashes when using network which should be fixed in 5.2.1).

    What can I do to find out what's wrong?

    Thanks!



  • Additional info, I have compiled Qt 5.2.2 for iOS from git with debugging enabled and now I get

    ASSERT failure in QVector<T>::operator[]: "index out of range", file qvector.h, line 372




  • Moderators

    Hi,

    Qt 5.2.2 is not released, so you might have an incompatible combination of revisions across your repos.

    I recommend using officially-released versions.

    [quote]I’ve tried to update from Qt 5.2.0 to Qt 5.2.1 but my application started crashing on almost every state change.[/quote]How did you update? Did you clean your build tree after updating?



  • [quote author="JKSH" date="1392899913"]Hi,

    Qt 5.2.2 is not released, so you might have an incompatible combination of revisions across your repos.

    I recommend using officially-released versions.
    [/quote]

    I've also tried the same with official release 5.2.1 and the result is very similar.

    [quote author="JKSH" date="1392899913"]How did you update? Did you clean your build tree after updating?[/quote]

    Yes, I use the recommended way:

    git pull
    git submodule sync
    git submodule update --recursive
    git submodule foreach --recursive "git clean -dfx"


  • Moderators

    Did you clean your project after updating?



  • [quote author="JKSH" date="1392903942"]Did you clean your project after updating?[/quote]

    Yes, I clean it for almost every build (I have very few c++ sources, almost everything is done in QML). Btw did you see the traceback (in bug report in JIRA)?


  • Moderators

    Hi,

    Sorry for the late reply. It looks like you found a bug indeed; the Qt devs are looking into it now.

    I hope the workaround works well with your app.


Log in to reply
 

Looks like your connection to Qt Forum was lost, please wait while we try to reconnect.