Bug #100237 Input string was not in a correct format at random times
Submitted: 16 Jul 2020 17:43 Modified: 21 Nov 2020 13:02
Reporter: Adrian with an A Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL for Windows: MySQL Notifier Severity:S3 (Non-critical)
Version:8.0.20 OS:Windows (Windows 10 2004)
Assigned to: MySQL Verification Team CPU Architecture:x86

[16 Jul 2020 17:43] Adrian with an A
Description:
MySQL 8.0.20 and other lower versions that I have tried throws out error pop-up randomly. I get a pop-up when doing nothing with my computer maybe once every 3 months on average. Windows version does not matter, if I am using mySQL server or not does not seem to matter. The message this time that looks like the other messages if I remember right when doing nothing with the computer:

Exception message:
Input string was not in a correct format.

Exception thrown by:
Program.MySQLNotifierAppExceptionHandler

Stack trace:
   at System.Number.ParseDouble(String value, NumberStyles options, NumberFormatInfo numfmt)
   at System.Convert.ToDouble(String value)
   at MySql.Notifier.Classes.Notifier.SettingsFileChanged(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)

How to repeat:
Install MySQL. Drink coffee for 3 months. See if you get a pop-up as the message above.
[16 Jul 2020 18:04] Adrian with an A
After posting this bug I noticed that 8.0.21 has been released and upgraded from 8.0.20. After maybe 5-10 minutes of being done upgrading I got by MySQL Notifier:

Exception message:
Input string was not in a correct format.

Exception thrown by:
Program.MySQLNotifierAppExceptionHandler

Stack trace:
   at System.Number.ParseDouble(String value, NumberStyles options, NumberFormatInfo numfmt)
   at System.Convert.ToDouble(String value)
   at MySql.Notifier.Classes.Notifier.SettingsFileChanged(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)
[16 Jul 2020 19:16] MySQL Verification Team
Thank you for the bug report. Are you able to attach here a screenshot of the error dialog?. Thanks.
[20 Jul 2020 2:26] Adrian with an A
I should have taken a screenshot, but I have not done it. Sorry. I will upload an image when it happens again. It might take a while.
[23 Jul 2020 11:59] MySQL Verification Team
Thank you for the feedback. Please attach the screenshot when you get the same error and change the status back to 'Open'.
[24 Aug 2020 1:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
[29 Sep 2020 9:23] Adrian with an A
Hello again,

I got a pop-up today when I started my computer and then after I restarted my computer again. Seems to not be exactly what my original post was about, but still interesting, I think.

Maybe this is the picture you are looking for:

https://imgur.com/1XXYOH3
[29 Sep 2020 9:24] Adrian with an A
Version of MySQL has changed:

8.0.20 -> 8.0.21.

Just so you know.
[21 Oct 2020 13:02] MySQL Verification Team
Please try latest version i.e 8.0.22. Thanks.
[22 Nov 2020 1:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".