Important: Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

nested QtConcurrent::map runs into deadlock



  • I ran into the issue documented here: https://bugreports.qt.io/browse/QTBUG-72872

    So I updated Qt to version 6.2.1 on my machine and I still run into the deadlock when using nested QtConcurrent::map.

    In the bug report it says "fixed in dev". Does this mean it is not yet merged/available in Qt 6.2.1?



  • @Heike
    My understanding is from the top of the bug report:

    Fix Version/s:

    5.15.7, 6.2.1, 6.3.0 Feature Freeze

    And in the History:

    qtgerritbotGerrit Bot made changes - 15 Sep '21 16:57

    Commits 1afd562b0b0bbba02575aa79601f0fae555cfa19 1afd562b0b0bbba02575aa79601f0fae555cfa19 7cd69f9af057f4b48b259004b032f241b72f0de9 (qt/qtbase/6.2)

    Fix Version/s 6.2.1 [ 19721 ]



  • I can see that the submodule qtbase has been updated on Sep 15th.

    commit 8f77aad620d6f8373a3a04fa0fc7ba9e6391575e
    Author: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
    Date:   Wed Sep 15 12:29:23 2021 +0300
    
        Update submodules on '6.2' in qt/qt5
        
        Change-Id: I84d860988a29673b3e6acdb2c97a06d4f175d9f6
        Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
    
    commit 606219e8aeb3da87fa1a366d4c4c37a45e48211b
    Author: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
    Date:   Wed Sep 15 03:10:25 2021 +0300
    
        Update submodules on '6.2' in qt/qt5
        
        Change-Id: Ic29a3336f09138631bbdd3204fd62aa45677242d
        Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
    
    

    And my submodule qtbase is pointing to

     9fa805f7f8dfe96d561e9ed3170770ad768baf93 ../qtbase (v6.2.1)
    

    and I still run into a deadlock. So the fix has been merged in, but isn't fixed properly then, correct?


  • Lifetime Qt Champion

    @Heike said in nested QtConcurrent::map runs into deadlock:

    So the fix has been merged in, but isn't fixed properly then, correct?

    Please provide a minimal, compilable example to reproduce the issue then. Best directly in the bug report. But please update to latest (6.2.2 I guess) before.


Log in to reply