Bug 383972

Summary: The peerstimeline proxy order is unstable/racy
Product: [Unmaintained] ring-kde Reporter: Emmanuel Lepage Vallée <emmanuel.lepage>
Component: generalAssignee: Emmanuel Lepage Vallée <emmanuel.lepage>
Status: RESOLVED FIXED    
Severity: normal    
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Emmanuel Lepage Vallée 2017-08-24 20:55:40 UTC 
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.