https://bugs.kde.org/show_bug.cgi?id=383972

            Bug ID: 383972
           Summary: The peerstimeline proxy order is unstable/racy
           Product: ring-kde
           Version: unspecified
          Platform: Other
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: elv1...@gmail.com
          Reporter: elv1...@gmail.com
  Target Milestone: ---

The peerstimelinemodel used by the left pane is prone to race conditions when
the applications load. The individual peer timeline too (not to be confused
with the peerS timeline).

This is caused by the deduplication algorithm and seems to have regressed with
all the recent memory managment changes that affected the loading order. The
race did exist before, but as the loading order was different, it was unlikely
(but as stree tests showed, not impossible). With the current HEAD commit,
there is about a 50/50 chance of being wrong.

This is in itself good news, as it shows the loading is a bit saner. However it
has to be fixed as it renders the app unusable. The items that should be at the
top can only be accessed using the search feature.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to