eq.gimasoft.com

I'm in a raiding guild, each time I load up Gina it crashes with the following report:

Object reference not set to an instance of an object.
at GimaSoft.Business.GINA.MatchHelper.IsMatch(String str)
at GimaSoft.Business.GINA.TriggerFilter.IsMatch(String str)
at GimaSoft.Business.GINA.GINACharacter.ProcessText(String str)
at GimaSoft.Business.GINA.GINACharacter.ProcessStream(StreamReader sr)
at GimaSoft.Business.GINA.GINACharacter.LogFileWatcher_Changed(Object sender, FileSystemEventArgs e)
at System.IO.FileSystemWatcher.OnChanged(FileSystemEventArgs e)
at System.IO.FileSystemWatcher.NotifyFileSystemEventArgs(Int32 action, String name)
at System.IO.FileSystemWatcher.CompletionStatusChanged(UInt32 errorCode, UInt32 numBytes, NativeOverlapped* overlappedPointer)
at System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32 errorCode, UInt32 numBytes, NativeOverlapped* pOVERLAP)

Crash version: 1.0.24.3

Prior to this, gina was working perfect. Then I tried moving some triggers around in groups to make sense and all of a sudden the whole thing is screwed up. Please help, it's critical for me to raid with.

Also, this bug only occurs when I add a log file to monitor. If it has no character set up to monitor it is absolutely fine.

I am getting same error and same issue: Gina crashed when starting monitoring log.
Something to do with new windows 10 update? I tried updating and rolling back and same issue.

I get the same issue and have a similar crash report with german texts so it's no GINA thing but something installed with / in Windows.

Gina can run for a minute or so but then crashes, writing the report cited above into the GINACrash.txt.

I had no crashes yesterday but there was nothing updated in Windows I noticed. I'm searching further what could be the problem.

I am having the exact problem. I was in the middle of setting up a new character. Soon as a trigger for that new toon "fired" it threw that error code. Light research says it's trying to find a Null value. I think it's having issues locating the correct log file?

Apparently it's a date formatting issue on the logs for dates of the 1st to the 9th. If you set your system date to the 10th there are no problems.

You know what... Before it crashed I had noticed something strange with the Dates and you are correct. Changing the Date did indeed work

This appears to be caused by the date losing the leading zero

[Sun Apr 01 13:31:35 2018]
[Tue May 1 11:53:33 2018]

This date-changing workaround might cause other problems.
If this is the problem, the root of it lies in EQ which formats the date this way.

I checked if EQ didn't do the date format like this last months. Previously EQ wrote "Feb 01", now it's "May 1" (two spaces).

As note Gina is still working for me but the matched text now includes the date and time

[Tue May 1 11:33:27 2018] You deliver a critical blast! (92076)

When before it was

You deliver a critical blast! (106032)