Qt Forum

    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Unsolved

    Call for Presentations - Qt World Summit

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

    Mobile and Embedded
    2
    3
    2639
    Loading More Posts
    • 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
      kottkungen last edited by

      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 Reply Quote 0
      • K
        kottkungen last edited by

        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 Reply Quote 0
        • A
          apic @kottkungen last edited by

          @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 Reply Quote 0
          • First post
            Last post