Constant crashing

[obuw]

The new version seems to be crashing constantly, upon receipt of a message. Not sure if it is possible to provide an error log?

[NickReinlein]

I am also getting this. I looked and didn't see a log but can provide one if I know where to look.

I have default settings on Windows 7 64-bit.

[Kapps]

Do either of you have Minimize on Startup enabled? It's not enabled by default.

[obuw]

I did, yeah. But I did suspect it might have something to do with it (since it's one of the few added things in the new version), so I doubleclicked the tray icon to open the window. Still crashed later on.

(I didn't try disabling the option completely. But I'm now back to 1.9 which works fine.)

[Kapps]

Ahh there we go, able to duplicate the issue now. There's no window created yet when minimize on startup is enabled, so the stuff that relies on the window handle for communicating ends up crashing it. I'll put out a fix for that shortly, but the crashing later even if you double-click the tray is odd... that shouldn't be the case here because when you double-click it it does get created.

[obuw]

Maybe the variable doesn't get initialized properly on double click or something? Or perhaps I'm confusing my steps. Either way I'll test with the new version once it's out, and let you know if I get any more crashes.

[Kapps]

Should hopefully be fixed now in 2.0b (https://github.com/Kapps/PoEWhisperNotifier/releases/tag/v2.0b). If it's not, I added logging on unhandled exceptions, which really should have existed before. :P

[NickReinlein]

Sorry I had it enabled also. I will try out the new version. Thank you!!

[RyuuOujiXS]

New version still crashes. It'll even crash while running with the window up. It'll just freeze and stop responding. Have to end task.

Errors are... 3/31/2017 8:08:17 PM: System.ObjectDisposedException: Cannot access a disposed object. Object name: 'Main'. at System.Windows.Forms.Control.MarshaledInvoke(Control caller, Delegate method, Object[] args, Boolean synchronous) at System.Windows.Forms.Control.Invoke(Delegate method, Object[] args) at PoEWhisperNotifier.Main.ProcessMessage(MessageData obj) in C:\src\PoEWhisperNotifier\PoEWhisperNotifier\Main.cs:line 173 at PoEWhisperNotifier.LogMonitor.RunReadLoop() in C:\src\PoEWhisperNotifier\PoEWhisperNotifier\LogMonitor.cs:line 188 at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading.ThreadHelper.ThreadStart()

...and...

3/31/2017 6:56:48 AM: System.InvalidOperationException: Invoke or BeginInvoke cannot be called on a control until the window handle has been created. at System.Windows.Forms.Control.MarshaledInvoke(Control caller, Delegate method, Object[] args, Boolean synchronous) at System.Windows.Forms.Control.Invoke(Delegate method, Object[] args) at PoEWhisperNotifier.Main.ProcessMessage(MessageData obj) in C:\src\PoEWhisperNotifier\PoEWhisperNotifier\Main.cs:line 173 at PoEWhisperNotifier.LogMonitor.RunReadLoop() in C:\src\PoEWhisperNotifier\PoEWhisperNotifier\LogMonitor.cs:line 188 at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading.ThreadHelper.ThreadStart()

[Kapps]

This may hopefully actually be fixed in the newest release. If it's not, then I'm honestly pretty stumped. I can't replicate this at all no matter what I do.