Ticket #975 (new defect)

Opened 2 years ago

Last modified 2 weeks ago

UI stops updating/redrawing after use

Reported by: cheers Assigned to: timothy
Priority: highest Component: Colloquy (GUI)
Version: Latest 2.1 Severity: major
Keywords: Cc: spork, pfibiger

Description

After some period of time (yesterday it took all day, today it froze within 20 minutes of launch), I'm seeing a complete stop in UI updates. The app is still responsive, I can select between tabs, and if I switch between them I see more lines of chat, and anything I typed in the text field before I switched away from the tab (ie: I get a 1-time update), but the cursor doesn't blink, chat doesn't scroll, and typing provides no visual feedback until I switch away from a tab and back to it.

I'm using the bland style, if that helps. I did have a variant that I created based on the faq suggestion to block channel enter & part messaged. I've just set myself back on default bland, and will report back if it doesn't happen again.

Change History

01/24/07 15:59:38 changed by cheers

reproed with default bland style

06/20/07 10:46:00 changed by arcfide

Have you attempted to use the /reload style trick?

(follow-up: ↓ 4 ) 08/16/07 04:34:35 changed by Msturm10

I can confirm this bug. when I start Colloquy, I don't see any messages in the chat windows (neither messages I type or messages typed by others). After doing /reload style, everything works fine. I think this is a pretty nasty bug, and should be resolved as quickly as possible.

(in reply to: ↑ 3 ) 08/16/07 12:05:29 changed by Rinoa

Replying to Msturm10:

I can confirm this bug. when I start Colloquy, I don't see any messages in the chat windows (neither messages I type or messages typed by others). After doing /reload style, everything works fine. I think this is a pretty nasty bug, and should be resolved as quickly as possible.

Your issue is an entirely different one. They are talking about when actively chatting. You are talking about upon join. What you have is #576.

09/17/07 10:35:09 changed by pfibiger

just to add a little data, i've just started seeing what i believe is this same bug only after getting the auto-update of the most recent build.

i'm more or less unable to get any updates once i join a channel. the roster on the left doesn't update, i see no typed messages, /reload style does nothing for me. It also doesn't appear to be related to auto-joining.

(follow-up: ↓ 7 ) 09/19/07 14:02:15 changed by spork

Same here. Happened after the update. Not only do I have #576, but it seems like most of the time nothing is updating. From what I can see it looks like I'm connected, but no one sees my messages - they echo back to me, but that's about it.

I don't know if this is silc-specific or not, I only use colloquy for silc, not irc.

The roster does not reflect reality either, FWIW.

The /reload style trick does not do anything, nor does disconnecting/reconnecting.

Building the old cli silc-client from fink now, I need silc for work.

(in reply to: ↑ 6 ) 09/19/07 14:26:00 changed by akempgen

Replying to spork:

Same here. Happened after the update. Not only do I have #576, but it seems like most of the time nothing is updating. From what I can see it looks like I'm connected, but no one sees my messages - they echo back to me, but that's about it. I don't know if this is silc-specific or not, I only use colloquy for silc, not irc. The roster does not reflect reality either, FWIW. The /reload style trick does not do anything, nor does disconnecting/reconnecting. Building the old cli silc-client from fink now, I need silc for work.

that is indeed silc specific (#1064), and not the bug described here.

the silc problem is fixed in svn, so you could just build colloquy from Source Code instead of using cli silc

09/20/07 15:20:30 changed by spork

Any chance you guys could just tag and build a release fixing the silc bug?

DIY build looks non-trivial for the average Mac user.

11/15/08 04:27:27 changed by grahamperrin

  • cc set to spork, pfibiger.
  • severity changed from blocker to major.

Is this still an issue for users of Colloquy 2.1 (3761)?