pluginlog.txt size filling up SSD

Hello

I really like this plugin. I use it to trigger Mackie control. However, there is a serious bug.

The pluginlog.txt builds up its size quickly. I happened to see my OS getting slow suddenly. That file was filling up becoming more than 100GB. My SSD life expectancy would be shortened if with this bug for a while.

I double checked if any of my commands are with "extended-logging", but none. But in some cases, it starts to build up quickly. I couldn't look into the contents of it, since it was too huge to open.

Please put an config option to totally turn off logging. Otherwise, I should give up on this plugin.

I had to delete that huge pluginlog.txt file. Now I am looking at that file and it isn't growing. I am sure it gets triggered at some point.

I looked into the archived log files at "C:\Users\user\AppData\Roaming\Elgato\StreamDeck\Plugins\se.trevligaspel.midi.sdPlugin\logs\log.004.txt", for example, and found a repetition of error, which counted up to 300MB.

2021-05-06 10:59:53.967 Error       4.27ms DawController    HandleConnection              [Exception: System.NullReferenceException: Object reference not set to an instance of an object.
   at StreamDeck_Midi.DawController.<>c.<HandleConnection>b__18_2(MidiInputDeviceItem d) in C:\Projects\StreamDeck-Midi - Core\StreamDeck-Midi\MIDIController\DawController.cs:line 173
   at System.Linq.Enumerable.WhereListIterator`1.MoveNext()
   at System.Linq.Enumerable.TryGetFirst[TSource](IEnumerable`1 source, Boolean& found)
   at System.Linq.Enumerable.FirstOrDefault[TSource](IEnumerable`1 source)
   at StreamDeck_Midi.DawController.HandleConnection() in C:\Projects\StreamDeck-Midi - Core\StreamDeck-Midi\MIDIController\DawController.cs:line 173]
2021-05-06 10:59:53.968 Error       3.86ms DawController    HandleConnection              [Exception: System.NullReferenceException: Object reference not set to an instance of an object.
   at StreamDeck_Midi.DawController.<>c.<HandleConnection>b__18_2(MidiInputDeviceItem d) in C:\Projects\StreamDeck-Midi - Core\StreamDeck-Midi\MIDIController\DawController.cs:line 173
   at System.Linq.Enumerable.WhereListIterator`1.MoveNext()
   at System.Linq.Enumerable.TryGetFirst[TSource](IEnumerable`1 source, Boolean& found)
   at System.Linq.Enumerable.FirstOrDefault[TSource](IEnumerable`1 source)
   at StreamDeck_Midi.DawController.HandleConnection() in C:\Projects\StreamDeck-Midi - Core\StreamDeck-Midi\MIDIController\DawController.cs:line 173]
2021-05-06 10:59:53.968 Error       3.72ms DawController    HandleConnection              [Exception: System.NullReferenceException: Object reference not set to an instance of an object.
   at StreamDeck_Midi.DawController.<>c.<HandleConnection>b__18_2(MidiInputDeviceItem d) in C:\Projects\StreamDeck-Midi - Core\StreamDeck-Midi\MIDIController\DawController.cs:line 173
   at System.Linq.Enumerable.WhereListIterator`1.MoveNext()
   at System.Linq.Enumerable.TryGetFirst[TSource](IEnumerable`1 source, Boolean& found)
   at System.Linq.Enumerable.FirstOrDefault[TSource](IEnumerable`1 source)
   at StreamDeck_Midi.DawController.HandleConnection() in C:\Projects\StreamDeck-Midi - Core\StreamDeck-Midi\MIDIController\DawController.cs:line 173]

and so on.

Ok, thanks.

It's the bug I describe here but I had the impression that it only affected the log size if extended logging was enabled.


To stop the logging, please verify that the midi ports defined for the Mackie Control action actually exists - the massive logging is caused by a bug when the defined ports are not present in the computer  (...I don't remember if you need to restart Stream Deck after creating the ports...)

Sorry about that problem. Thanks for reporting it, I will try to get a fix released as soon as possible.

A fixed version of the plugin is sent to Elgato for publishing. I don't know what time zone they are operating in but I presume they will take care of it as soon as they see my request.

The fixed version is now released.

Admin wrote:Ok, thanks.

It's the bug I describe here but I had the impression that it only affected the log size if extended logging was enabled.


To stop the logging, please verify that the midi ports defined for the Mackie Control action actually exists - the massive logging is caused by a bug when the defined ports are not present in the computer  (...I don't remember if you need to restart Stream Deck after creating the ports...)

Sorry about that problem. Thanks for reporting it, I will try to get a fix released as soon as possible.

Oh, now I get it. The launch order has influence on whether the bug is triggered or not.

The loopmidi launcher and streamdeck are started when the OS boots up, but if the order is streamdeck and then loopmidi, your MIDI plugins can't find that midi port and hence triggers this bug.

Admin wrote:The fixed version is now released.

Thank you for the fix. I will try it when at home.

cjunekim wrote:Oh, now I get it. The launch order has influence on whether the bug is triggered or not.

The loopmidi launcher and streamdeck are started when the OS boots up, but if the order is streamdeck and then loopmidi, your MIDI plugins can't find that midi port and hence triggers this bug.

Well, yes...and no. That's actually a scenario I haven't thought about. But you're right, if Stream Deck started before loopMidi the bug temporary caused some additional logging until loopMidi started. I don't think it would have caused so much damage because it was only a brief moment. The main problem was if you created a Mackie Control button and never created the default ports that was assigned to it (or changed the ports for the button). That would cause excessive logging "for ever" and would have given the problems you had with your computer.

Hopefully that is a problem of the past now.