1137439 - Loop panel becomes partially unresponsive after attempting to rename room (intermittent)

Status: RESOLVED INCOMPLETE

(Hello (Loop) :: Client, defect)

Description

[Adam Roach [:abr]]

Both I and EKR had an experience, at roughly the same time, in which we attempted to rename a room. The name change was not reflected in the Loop panel, and then the panel became unresponsive in a very odd way:

This still worked:
- Switching between the rooms view and contact view still worked
- Attempts to start calls from the contacts view worked
- The "Available/Do Not Disturb" control worked and correctly updated the associated pref

This was broken:
- Attempts to open a room closed the panel but otherwise did nothing
- Attempts to rename a room caused no network traffic (but did update the panel)
- Clicking on "copy" caused the icon to change to a checkbox, but the URL was not copied to the clipboard

After I opened a new browser window, the loop panel in that window worked fine, and reflected the initial name change (but not subsequent ones attempted in the "broken" panel). The "broken" panel continued to function improperly.

Subsequent attempts to provoke this situation have not been successful. It seems likely that one of the servers was returning errors at this specific time, and it provoked the same behavior in both my client and EKRs.

Comment 1

[Mark Banner (:standard8)]

I think what's happened here is that somewhere in renaming the panel, there's been a action sent in the panel, and when the action was processed it caused an uncaught error.

The uncaught error then causes the dispatcher to stop working. This would cause the appearance reported where the rooms items were still broken, but the contact calls and the Available/Do Not Disturb to continue working.

I'm filing that bug separately as that's an easy fix.

I think we've possibly got an occasional issue with the rename somewhere that's causing this and I want to at least dig through the code paths to try and determine what it could be.

Comment 2

[Mark Banner (:standard8)]

Unfortunately I think we should have got to investigate this sooner. I can't think of any specific issues now, and we've also removed the rename in the panel. We did fix bug 1137469 which should have stopped any complete failures.

So I think I'm going mark this as incomplete, as we don't have enough info/ideas to move it forward.