Ticket #563 (new bug)

Opened 4 months ago

Last modified 4 weeks ago

Chat log missing time

Reported by: gnomre Owned by: unassigned
Priority: minor Milestone: 0.1 basic functionality
Component: program logic Version: all
Keywords: Cc:

Description

After reconnecting to the lobby server due to a disconnect on my end without restarting SpringLobby?, chat was no longer logged until it crashed without any warning or error. Logging resumed after I restarted SpringLobby?. This is with SL v0.0.1.10312 on Windows XP SP2.

Here's a timeline of events to be clear:
[2008-07-31 15:53] SpringLobby? started

[2008-08-01 00:54] Connection failure (my entire connection, not just SpringLobby?). SL registers this as [00:54] ** Server ** Chat closed.

[2008-08-01 02:25] Connection comes back up. I reconnect SL, logs report: ### Session Closed at [2008-08-01 02:25]

[2008-08-01 sometime between 15:32 and 16:07] SpringLobby? disappears entirely, the entire process gone without any error message whatsoever

[2008-08-01 16:07] I notice SL has crashed and restart it, logging resumes

Attachments

Change History

Changed 4 months ago by koshi

  • version set to windows
  • component changed from program general to program logic
  • milestone set to 0.1 basic functionality

Changed 5 weeks ago by koshi

  • owner changed from - to koshi

Changed 5 weeks ago by anonymous

  • priority changed from major to minor
  • version changed from windows to all

confirmed. seems chalog pointer gets invalidated on disconnect or reconnect, haven't found where that happening yet

Changed 5 weeks ago by anonymous

this is extra weird, the bool ChatLog::WriteLine?(const wxString& text) doesn't not fail after reconnect. even the real write in line 102 of chatlog .cpp returns success. yet there is no new text in the logfile. not even after forcing a flush after every write

Changed 5 weeks ago by anonymous

  • owner changed from koshi to unassigned

http://filebin.springlobby.info/strace.log
can't make anything of that either

Changed 4 weeks ago by koshi

will prolly become a non-issue after #327 is implemented

Add/Change #563 (Chat log missing time)

Author



Change Properties
<Author field>
Action
as new
as The resolution will be set. Next status will be 'closed'
to The owner will change. Next status will be 'new'
The owner will change to anonymous. Next status will be 'assigned'
 
Note: See TracTickets for help on using tickets.