Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. QML and Qt Quick
  4. QTBUG-15191 Memory Leak with XMLListModel, how to workaround in Qt4.7.0 on Maemo?
QtWS25 Last Chance

QTBUG-15191 Memory Leak with XMLListModel, how to workaround in Qt4.7.0 on Maemo?

Scheduled Pinned Locked Moved QML and Qt Quick
3 Posts 2 Posters 2.3k 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.
  • S Offline
    S Offline
    scifi.guy
    wrote on last edited by
    #1

    Cross-posting from qt-qml mailing list since I didn't get any reply. Sorry for the crime.

    I developed a widget for Maemo which is dependent on XMLListModel. The widget
    pulls stock quotes from Yahoo finance in regular intervals. Due to a known issue
    with XMLListModel [1], there is a memory leak every time the model is reloaded.
    However, I have to reload the model to get the latest quotes.

    I am aware that this memory leak will be fixed in Qt 4.8.0. However, I don't
    know if/when Maemo will get the Qt update. Until then, I am looking for a
    workaround to avoid the memory leak. Here is a skeleton of my code[2]. Can you
    give me any suggestions?

    ~Sudheer

    [1] - http://bugreports.qt.nokia.com/browse/QTBUG-15191
    [2] - http://pastebin.com/fpPmKj1L

    1 Reply Last reply
    0
    • H Offline
      H Offline
      hoanghua
      wrote on last edited by
      #2

      Hi,

      I'm having exactly the same issue with XmlListModel, have you found any solution yet?

      Thanks

      1 Reply Last reply
      0
      • S Offline
        S Offline
        scifi.guy
        wrote on last edited by
        #3

        @hoanghua - I just stopped using XMLListModel. Now I use a ListModel and refresh it by removing all entries and populating with output from XmlHttpRequest through JavaScript. Painful to parse responseXML in JavaScript but it is much better than continuously leaking memory.

        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