One of the Jabber users in my office switched from
Kunani (not sure of version) to Jabber IM
(v-1.7.0.14). The first thing that was noticed was
that my profile showed up as a pending
subscription until I subscribed to him for the
second time. Before I subscribed again,
Jabbernaut would crash with a Type 2 error
whenever I tried to send a message to him.
I am the only one in the office using Jabbernaut,
and it was working flawlessly, but now it seems to
crash whenever I use with any degree of regularity.
We are using the JabberCOM (v-2.3.1.4) client, and
the only other odd activity is certain profiles seem
to constantly change between offline and online,
without any actual user involvement.
I have tried deleting preferences and reinstalling. I
am having the problems with both the 0.5.5 and
the 0.5.6b1 client. The next step will be to totally
delete my profile from JabberCOM, and see if that
helps any.
Logged In: YES
user_id=12935
Hm, that is very strange. I'd like to ask you to contact me via jabber (JID blue_fingolfin@jabber.org or black_fingolfin@jabber.org)
It seems as if JabberIM might send something that Jabbernaut chokes on. Maybe if you send me via email the full XML in/out log (stripped of any passwords of course), I could do something about it.
Right, it crashes, but maybe you can enlarge the XML in window, then do the "crashing" action, and it will print into the XML log window the last incoming data. This then you could copy down manually, and tell me what it got last (i.e. what crashed)
Logged In: NO
Alright, sorry I did not get back soner...I have pretty much given
up on trying to use Jabbernaut in the office anymore, as it crashes
several times a day. All the crashes occur when I am : 1) Typing a
message or reply to a message, or in a chat window. 2) when a
message is sent to me, and Jabbernaut comes to the front. I will
see the message for a split second then the machine will crash.
I have been running MacsBug while the crashes occured, and they
all seem to be corruption in the memory heap. All the crashes lead
to either having to issue the "rs" command in MacsBug, or in most
cases, having to hit the reset button on the Mac. If you would like
copies of the "stdlog" from the crashes, I can provide those. If I
get some free time where I am not doing any work, I will try to get
ahold of you through Jabber.