search

kauffman12 / EQLogParser

Everquest Log Parser for Live and TLP servers
Apache License 2.0
63 stars 21 forks source link

Exception recorded in EQLogParser.log #176

Closed cluefone closed 4 months ago

cluefone commented 4 months ago

I'm seeing the following in 2.2.20 when starting the app. I typically have multiple characters with active trigger monitoring, but this error occurs with any selected. The startup is clean with no characters checked in the Trigger Manager.

2024-05-26 13:57:17,935 [1] ERROR EQLogParser.App - AppDispatcherUnhandledException 2024-05-26 13:57:17,936 [1] ERROR EQLogParser.App - Object reference not set to an instance of an object. System.NullReferenceException: Object reference not set to an instance of an object. at EQLogParser.TriggersCharacterView.RefreshData() at EQLogParser.TriggersCharacterView.UpdateStatus() at EQLogParser.TriggersCharacterView.StatusTimerTick(Object sender, EventArgs e) at System.Windows.Threading.DispatcherTimer.FireTick() at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs) at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)

kauffman12 commented 4 months ago

Do you leave Trigger Manager open when you close the app? Just curious.

On Sun, May 26, 2024, 4:04 PM cluefone @.***> wrote:

I'm seeing the following in 2.2.20 when starting the app. I typically have multiple characters with active trigger monitoring, but this error occurs with any selected. The startup is clean with no characters checked in the Trigger Manager.

2024-05-26 13:57:17,935 [1] ERROR EQLogParser.App - AppDispatcherUnhandledException 2024-05-26 13:57:17,936 [1] ERROR EQLogParser.App - Object reference not set to an instance of an object. System.NullReferenceException: Object reference not set to an instance of an object. at EQLogParser.TriggersCharacterView.RefreshData() at EQLogParser.TriggersCharacterView.UpdateStatus() at EQLogParser.TriggersCharacterView.StatusTimerTick(Object sender, EventArgs e) at System.Windows.Threading.DispatcherTimer.FireTick() at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs) at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)

— Reply to this email directly, view it on GitHub https://github.com/kauffman12/EQLogParser/issues/176, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAF4KB5DNOZ2JDMN3LHGUA3ZEI54VAVCNFSM6AAAAABIKB3NPCVHI2DSMVQWIX3LMV43ASLTON2WKOZSGMYTOOJRGI2DANQ . You are receiving this because you are subscribed to this thread.Message ID: @.***>

SilvenaRogue commented 4 months ago

Not OP

I had that same thing pop in my error log (posted in my report about being You in the archived log) I always leave Trigger Manager open when closing the app.

cluefone commented 4 months ago

Yes, I always keep the Trigger Manager open. I don't close anything manually, and it is one of the tabs that persists through a restart.

kauffman12 commented 4 months ago

Ok. Yeah it's probably just a timing issue. The window is loading slowly on some systems. After the log readers are already sending status. I'll put in some extra checks for that. It shouldn't be a big issue.

kauffman12 commented 4 months ago

Try 2.2.21 to see if these go away.