Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. General talk
  3. Brainstorm
  4. Spooky Qt Event Loop

Spooky Qt Event Loop

Scheduled Pinned Locked Moved Brainstorm
6 Posts 4 Posters 4.2k Views
  • 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.
  • V Offline
    V Offline
    vishwajeet
    wrote on 30 Jul 2010, 10:08 last edited by
    #1

    Has anybody noticed from Qt4.6.0 onwards, Qt's event loop has been acting little weird.

    Was there any modification or some changes ?

    One impact for sure is on QLocalSocket in asynchronous communication.

    Born To Code !!!

    1 Reply Last reply
    0
    • T Offline
      T Offline
      tobias.hunger
      wrote on 30 Jul 2010, 10:38 last edited by
      #2

      What makes it appear to be spooky?

      1 Reply Last reply
      0
      • V Offline
        V Offline
        vishwajeet
        wrote on 31 Jul 2010, 12:04 last edited by
        #3

        I have a example but i can not share with public forum i guess.

        But here try to something like this, write your firefox or safari browser plugin using Qt and communicate it with QLocalSocket. Now in asynchronous communication, you simply stop getting messages from server. This is case with 4.6 higher. if you run same application with Qt 4.5 things works fine. Now not sure about where exactly the prob is but 1 timer that calls processEvents() function does a trick, everything starts working.

        There are other examples as well but trying to dig into it.

        Born To Code !!!

        1 Reply Last reply
        0
        • D Offline
          D Offline
          DenisKormalev
          wrote on 31 Jul 2010, 16:09 last edited by
          #4

          Maybe you can provide some test application written especially to show this bug? Without revealing closed source you have.

          1 Reply Last reply
          0
          • T Offline
            T Offline
            tzander
            wrote on 9 Aug 2010, 08:52 last edited by
            #5

            I have not seen something like that, there were some fixes made in QIODevice so maybe you hit one of those that made a previous bug in your app stand out.

            But without the failing code that is really hard to say :)

            1 Reply Last reply
            0
            • V Offline
              V Offline
              vishwajeet
              wrote on 9 Aug 2010, 15:22 last edited by
              #6

              Thats true, Let me reproduce that with code, will raise a bug

              Born To Code !!!

              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