Uploaded image for project: 'Qt Mobility'
  1. Qt Mobility
  2. QTMOBILITY-1046

Declarative landmark proximity filter eats memory

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: P1: Critical P1: Critical
    • 1.1.1
    • 1.1.0
    • Location
    • None
    • Any QML platform
    • 5bb9cdcc5bed1eb8f8f4c547445730ca13428bdb

      If the 'center' property of the LandmarkProximityFilter is bound to a coordinate (e.g. PositionInfosource),
      every time the coordinate changes, LandmarkProximityFilter will internally bind for changes in lat/lon.

      Since with PositionInfosource the actual coordinate object instance remains the same (won't be deleted in between), this means that the filter binds couple new connections on each update. Run the app for minute with one second update interval, and there are already 120 connections.

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

            juvuolle Juha Vuolle (closed Nokia identity) (Inactive)
            juvuolle Juha Vuolle (closed Nokia identity) (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved:

                There are no open Gerrit changes