IceChat Forums

IceChat 9 => IceChat 9 Problems => Topic started by: Patrik356b on October 24, 2012, 07:33:23 AM

Title: Graphical bug.
Post by: Patrik356b on October 24, 2012, 07:33:23 AM
Well this has happen quite a few time and it is very annoying.

On a fairly active channel you say something and the message does get sent, and is saved to the logs.
But you won't see it.

If this is normal chat:
<Guest12> Hello
<You> Hi
<Guest24> Hey

Then sometimes this happens:
<Guest12> Hello
<Guest24> Hey

While this happens this is what the logs say:
<Guest12> Hello
<You> Hi
<Guest24> Hey


In conclusion: Others see your message, you don't.


This is on IceChat RC 5.0
Title: Re: Graphical bug.
Post by: Snerf on October 24, 2012, 10:15:32 AM
So you do not see the message at all, or is it you are looking back in the scroll buffer and have noticed it has disappeared?
Title: Re: Graphical bug.
Post by: Patrik356b on October 24, 2012, 05:30:45 PM
It does not appear simply, it has never happened when scrolling up/down
Title: Re: Graphical bug.
Post by: Snerf on October 24, 2012, 09:58:06 PM
Thanks, I'll see what could be causing it. Should be a fun one to try and narrow down.
Title: Re: Graphical bug.
Post by: Patrik356b on October 25, 2012, 03:10:36 PM
Okay now this time it was different:
<You> Hi
* <Guest19> quit channel #electronics


But this is what actually happened:
* <Guest16> joined channel #electronics
<You> Hi
* <Guest19> quit channel #electronics


From what I can see the timing between messages for this to occur is 0-5 seconds.
Title: Re: Graphical bug.
Post by: Snerf on October 25, 2012, 04:38:30 PM
Is it happening fairly consistently?
Title: Re: Graphical bug.
Post by: Snerf on October 27, 2012, 06:01:05 PM
Just curious as to how often it is happening, for me to try and narrow down the issue.
Title: Re: Graphical bug.
Post by: Patrik356b on October 27, 2012, 10:00:31 PM
It appears each 2-3 days when running the client 24/7.

As a sidenote; My windows installation broke 2 days ago. It may be related due the timing of issues.
Title: Re: Graphical bug.
Post by: Snerf on December 17, 2012, 03:23:07 PM
Have you noticed at all, if it seems to appear more in lines that are highlited by the highlite plugin?
Title: Re: Graphical bug.
Post by: Patrik356b on January 02, 2013, 04:23:20 AM
I haven't tried unloading that plugin and i haven't seen this problem in a week now.

Unloading it had no effect on the other highlight issue mentioned here: http://www.icechat.net/forums/index.php?topic=1661.msg6926#msg6926
Title: Re: Graphical bug.
Post by: Snerf on January 02, 2013, 06:03:01 PM
I am having a very hard time replicating this issue. Spent over an hour, and I did not find any issues.
I need something that can cause this problem more consistently, or I am just chasing ghosts.

Do you notice the problems in your channel log only?
Have you also opened debug.log, used the debug, and see the extra lines there as well?

Also, how do you notice the problem is occuring?
Do you have 2 different clients open, and see it happen right away, or look in the channel log, and see the line is missing later on?
Title: Re: Graphical bug.
Post by: Patrik356b on January 11, 2013, 09:05:01 AM
I'm only running a single client.

Last seen this issue today.

Unloading highlight plugin does not make a difference

It's a problem that's hard to trace, as today, the messages was sent while this happened but it wasn't logged to errors.log or the channel logs (and i still couldn't see the message I sent.)

Could not find the file debug.log yet either. However, I have found out that this is only something that happens when you chat normally. I have not seen this in a query, but it have never occurred on action messages.

I'll keep updating the topic when I find something.
Title: Re: Graphical bug.
Post by: Snerf on January 11, 2013, 09:45:21 AM
Is this happening when you are sending messages, or other channel messages coming through?
Title: Re: Graphical bug.
Post by: Patrik356b on January 11, 2013, 01:07:33 PM
It only happens when I send my messages sometimes

Found something in the console logs though:

Code: [Select]
[17:43.30] Error:ParseOutGoingCommand:Object reference not set to an instance of an object.:   at IceChat.FormMain.ParseOutGoingCommand(IRCConnection connection, String data)
[17:44.09] Error:ParseOutGoingCommand:Object reference not set to an instance of an object.:   at IceChat.FormMain.ParseOutGoingCommand(IRCConnection connection, String data)
[17:44.48] Error:ParseOutGoingCommand:Object reference not set to an instance of an object.:   at IceChat.FormMain.ParseOutGoingCommand(IRCConnection connection, String data)
[17:45.18] Error:ParseOutGoingCommand:Object reference not set to an instance of an object.:   at IceChat.FormMain.ParseOutGoingCommand(IRCConnection connection, String data)
[17:52.30] Error:ParseOutGoingCommand:Object reference not set to an instance of an object.:   at IceChat.FormMain.ParseOutGoingCommand(IRCConnection connection, String data)
[18:00.04] Error:ParseOutGoingCommand:Object reference not set to an instance of an object.:   at IceChat.FormMain.ParseOutGoingCommand(IRCConnection connection, String data)
[18:03.08] Error:ParseOutGoingCommand:Object reference not set to an instance of an object.:   at IceChat.FormMain.ParseOutGoingCommand(IRCConnection connection, String data)
Title: Re: Graphical bug.
Post by: Snerf on January 11, 2013, 05:54:45 PM
Oh, that is quite an interesting error.
That would most certainly cause a problem with a message not sending.

How are you moving between tabs?
Title: Re: Graphical bug.
Post by: Patrik356b on January 12, 2013, 03:18:38 PM
I'm not sure but i think I usually use the server tree, Haven't really gave that a though.
Title: Re: Graphical bug.
Post by: Snerf on January 12, 2013, 07:29:28 PM
Well, that error is basically saying it can not find a current connection wherever you are typing from.
And I had no idea that was even possible, to get a null connection.

So, yes, it has me puzzled.

What I can do is give you a special build, which has some extra error checking in it for this error, and perhaps we can narrow down the issue. Having it down to where it only seems to happen when you write messages is a big step forward already, I thought it was losing incoming messages.

If you come see me in #icechat2009 on quakenet, we can see about getting you a special build.

Title: Re: Graphical bug.
Post by: Snerf on January 26, 2013, 03:44:20 PM
Have you had any issues with the newer build?

Just curious if it has helped at all, and spit out any errors to you.

Thanks
Title: Re: Graphical bug.
Post by: Patrik356b on January 31, 2013, 03:32:56 AM
Found something now:

If you are on a channel and then change your nickname in Server Settings for that network, instead of using /nick <newnick> the bug is triggered.

It appeared randomly before though.

Console Error:
Code: [Select]
Session Start: to jan 31 12:17:59 2013
[12:17.59] Error:ParseOutGoingCommand:Channel:hmm:Object reference not set to an instance of an object.:   at IceChat.FormMain.ParseOutGoingCommand(IRCConnection connection, String data)
[12:27.31] Error:ParseOutGoingCommand:Channel:hmm...:Object reference not set to an instance of an object.:   at IceChat.FormMain.ParseOutGoingCommand(IRCConnection connection, String data)

Also, there was something in exceptions log file which could be related:
Code: [Select]
2012-09-26 09:02:01-The operation is not allowed on non-connected sockets.:   at System.Net.Sockets.NetworkStream.InitNetworkStream(Socket socket, FileAccess Access)
   at System.Net.Sockets.NetworkStream..ctor(Socket socket)
   at IceChat.IRCConnection.OnConnectionReady(IAsyncResult ar)
   at System.Net.LazyAsyncResult.Complete(IntPtr userToken)
   at System.Net.ContextAwareResult.CompleteCallback(Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Net.ContextAwareResult.Complete(IntPtr userToken)
   at System.Net.LazyAsyncResult.ProtectedInvokeCallback(Object result, IntPtr userToken)
   at System.Net.Sockets.BaseOverlappedAsyncResult.CompletionPortCallback(UInt32 errorCode, UInt32 numBytes, NativeOverlapped* nativeOverlapped)
   at System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32 errorCode, UInt32 numBytes, NativeOverlapped* pOVERLAP)

11/13/2012 02:18:29-There is an error in XML document (0, 0).:   at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events)
   at System.Xml.Serialization.XmlSerializer.Deserialize(TextReader textReader)
   at IceChat.FormMain.LoadOptions()
   at IceChat.FormMain..ctor(String[] args, Form splash)
   at IceChat.Program.Main(String[] args)

11/13/2012 02:18:48-There is an error in XML document (0, 0).:   at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events)
   at System.Xml.Serialization.XmlSerializer.Deserialize(TextReader textReader)
   at IceChat.FormMain.LoadOptions()
   at IceChat.FormMain..ctor(String[] args, Form splash)
   at IceChat.Program.Main(String[] args)

2012-11-14 22:10:18-There is an error in XML document (0, 0).:   at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events)
   at System.Xml.Serialization.XmlSerializer.Deserialize(TextReader textReader)
   at IceChat.FormMain.LoadOptions()
   at IceChat.FormMain..ctor(String[] args, Form splash)
   at IceChat.Program.Main(String[] args)

2012-11-14 22:10:23-There is an error in XML document (0, 0).:   at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events)
   at System.Xml.Serialization.XmlSerializer.Deserialize(TextReader textReader)
   at IceChat.FormMain.LoadOptions()
   at IceChat.FormMain..ctor(String[] args, Form splash)
   at IceChat.Program.Main(String[] args)

2012-11-14 22:10:43-There is an error in XML document (0, 0).:   at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events)
   at System.Xml.Serialization.XmlSerializer.Deserialize(TextReader textReader)
   at IceChat.FormMain.LoadOptions()
   at IceChat.FormMain..ctor(String[] args, Form splash)
   at IceChat.Program.Main(String[] args)
Title: Re: Graphical bug.
Post by: Snerf on January 31, 2013, 03:29:59 PM
Ok, I will take a look at it.
But this may be a new bug, not related at all to your current one. I am tinkering with how IceChat remembers nicks and such , and was in transition with the build I sent you.
Title: Re: Graphical bug.
Post by: Patrik356b on January 31, 2013, 03:33:34 PM
Aha. I see.

Nothing else seen yet
Title: Re: Graphical bug.
Post by: Snerf on January 31, 2013, 03:44:26 PM
Have you had the bug yet, with not seeing your own text?

EDIT: whoops, never mind that, I saw the "hmm" thing.
I can give you another build, so I can see where it is erroring more precisely.
It is seeing that you are in a channel, so that is good.