Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Mobile and Embedded
  4. Is the message "QLock::lock(): Identifier removed" anything I should be concerned about?
Forum Updated to NodeBB v4.3 + New Features

Is the message "QLock::lock(): Identifier removed" anything I should be concerned about?

Scheduled Pinned Locked Moved Mobile and Embedded
3 Posts 2 Posters 2.9k Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • K Offline
    K Offline
    kottkungen
    wrote on last edited by
    #1

    I have a platform with an optional secondary display. Since I want to separate the two displays I've split the code into two applications, one for the primary display and one for the secondary. I start them by running
    @
    ./app_1 -qws -display linuxfb:/dev/fb0 &
    if [ -e /dev/fb1 ]
    then
    ./app_2 -qws -display linuxfb:/dev/fb1 &
    fi
    @

    But now I started to see the output:
    @
    QLock::lock(): Identifier removed
    QLock::unlock(): Unlock without corresponding lock
    QLock::lock(): Identifier removed
    QLock::unlock(): Unlock without corresponding lock
    QLock::lock(): Identifier removed
    QLock::unlock(): Unlock without corresponding lock
    @

    Is this something I should be concerned about? Is this caused by running several qws:es? Or should I look for the error somewhere else?

    Thanks
    /Emil

    A 1 Reply Last reply
    0
    • K Offline
      K Offline
      kottkungen
      wrote on last edited by
      #2

      It does seem to be a problem, after a while one of the screen freezes. My guess is that the process deadlocks. It's been a while since I compiled Qt, and I don't have the config files. But from what I can see in my qconfig.pri it seems like most of the things are enabled. Does anyone have any advice on what to look for?

      1 Reply Last reply
      0
      • K kottkungen

        I have a platform with an optional secondary display. Since I want to separate the two displays I've split the code into two applications, one for the primary display and one for the secondary. I start them by running
        @
        ./app_1 -qws -display linuxfb:/dev/fb0 &
        if [ -e /dev/fb1 ]
        then
        ./app_2 -qws -display linuxfb:/dev/fb1 &
        fi
        @

        But now I started to see the output:
        @
        QLock::lock(): Identifier removed
        QLock::unlock(): Unlock without corresponding lock
        QLock::lock(): Identifier removed
        QLock::unlock(): Unlock without corresponding lock
        QLock::lock(): Identifier removed
        QLock::unlock(): Unlock without corresponding lock
        @

        Is this something I should be concerned about? Is this caused by running several qws:es? Or should I look for the error somewhere else?

        Thanks
        /Emil

        A Offline
        A Offline
        apic
        wrote on last edited by
        #3

        @kottkungen
        Hello kottkungen, I know this is an old post
        but did you solve this? I have exactly same configuration with two QWS applications
        on different fbs and exactly same error messages.

        Thank you for your help

        1 Reply Last reply
        0

        • Login

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • Users
        • Groups
        • Search
        • Get Qt Extensions
        • Unsolved