After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 753420 - ending up with an empty chatview hmm
ending up with an empty chatview hmm
Status: RESOLVED FIXED
Product: polari
Classification: Applications
Component: general
3.17.x
Other Linux
: Normal normal
: ---
Assigned To: Polari maintainers
Polari maintainers
Depends on:
Blocks:
 
 
Reported: 2015-08-09 16:55 UTC by Bastian Ilsø
Modified: 2015-10-07 17:02 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
the-consequence-of-alt-up-alt-down-fast (293.79 KB, image/png)
2015-08-09 16:55 UTC, Bastian Ilsø 		  Details
roomStack: Keep all views around (again) (2.60 KB, patch)
2015-10-07 17:02 UTC, Florian Müllner 		committed Details | Review

Description Bastian Ilsø 2015-08-09 16:55:11 UTC 
Created attachment 308980 [details]
the-consequence-of-alt-up-alt-down-fast

If I alt+up/alt+down really fast between rooms and end in the mid of some transition (not sure), it seems there's no chatView visible.
Comment 1 Simonas Kazlauskas 2015-09-24 13:35:18 UTC 
It is easier to reproduce with larger rooms.

A room with 1k users takes some considerable time to actually show up and quickly switching to and away from such room will reproduce the issue.

Pretty annoying.
Comment 2 Florian Müllner 2015-10-07 17:02:15 UTC 
The following fix has been pushed:
86915d6 roomStack: Keep all views around (again)
Comment 3 Florian Müllner 2015-10-07 17:02:21 UTC 
Created attachment 312838 [details] [review]
roomStack: Keep all views around (again)

Commit 13299455 worked around stack performance issues by only keeping
one or two (during transitions) visible children in the stack. However
this introduced a race condition where no view at all would be visible
when switching channels quickly, and GtkStack performance has improved
significantly, so revert that commit.