search

matoom / frostbite

MUD client for dragonrealms.
29 stars 17 forks source link

Latest build crashed - turning on logging - and garbled text on second app #16

Closed Dartellum closed 7 years ago

Dartellum commented 8 years ago

Also, when I open a second instance, the text is garbled. The second instance is in its on folder, so a separate executable. I did not have any challenges doing this with the older version.

matoom commented 8 years ago

I tried running two clients but did not experience any garbled text. I did not have Lich running though, is it something that is supported by Lich? Or just maybe some unfortunate circumstances that resulted both clients running on the same Lich connection?

I'll try running the new release build on my clean Ubuntu install and see if i get a crash out of it over extended period. It is certainly possible that there is something wrong with the release build in particular but there's again too many variables. I'll try Lichless at first. It's something to consider at least, the protocol parsing is very sensitive to any kind of malformed or missing tags, anything like that could easily cause a crash.

matoom commented 8 years ago

Also do you get a lot of use out of the familiar window? I wonder if that is something i need to focus on while testing. Under normal circumstances i have no text in there at all but i did some changes in for Empath wound parsing so, that's another possible trouble area.

Dartellum commented 8 years ago

I am a Warrior Mage, so familiar window is useful to me.

matoom commented 8 years ago

Well i tried that, i spent about half a day just spamming the familiar window. I had total around 10 days of uptime with no crashes, then i wanted to switch to Lich but ended up restarting after some technical difficulties. It ran just fine the first time, now every time i get a connection timeout from the server Lich will not start again until i uninstall everything and restart. I can't get it running for long enough to matter.

Plus, i'm starting to think it's not completely random and probably something you're doing differently. I think i need to do more focused testing.

Is there anything in particular you were doing when it crashed? Or settings wise, i don't think anything else will matter other than highlights. Do you have any special highlights? I don't think i've done a lot of testing with different regular expressions for example, could be something with that. And when i finally get Lich running, what kind of scripts are you usually running or maybe you even know the exact one you had running then it crashed? Also is there anything interesting in the debug log right after the crash? If there's anything wrong with message parsing and the crash was not too sudden, the last lines in the debug log could be pointing to the error.

Dartellum commented 7 years ago

It does not crash on the second instance. The text is just garbled. No settings or highlights yet.

Dartellum commented 7 years ago

The latest build, Version 1.4.1 beta, is working as expected. I will test over the next few days.

Dartellum commented 7 years ago

I have had the client close, or crash, four or so times. I will run from a terminal next time to capture what happens.

Dartellum commented 7 years ago

Working on this in another issue now.