Cycle 12, day #6:
On day #5, I did pause the loops playback at 3.5 loops and forgot to resume the playback accidentally. Keep in mind that I listen to those loops during my sleep. If I pause the playback, It is if I have go to the bathroom in the middle of night when I'm not 100% conscious...
I did realize the glitch when I was about to launch day #6 loops playback. So I completed day#5 loops followed by the day #6 6 loops. For a total of 8.5 loops on day 6. I guess that in the long run, things will even up...
My heap corruption investigation did lead to a very productive bug hunt. With the closer inspection, I did find another bug and another improvement opportunity.
If I add the JSON decoding improvement, that starts to be a lot of fixes and improvements...
I also completed my new test program that does reproduce the events that did lead to the crash... I did use an incremental approach... I was adding 1 step to it. Then I was running it to make sure that I got the exact same result than what I am seeing the server log then I was continuing by adding the next step. Everything was smooth and I kinda lost hope to be able to reproduce the problem. Until, I added the very last step that did happen before the crash...
And my test program did crash... I haven't started to analyze the test program crash but it feels like it is very promising. I may eliminate a serious bug that is triggered only in very specific conditions that I haven't understood yet...
This is so cool...
On day #5, I did pause the loops playback at 3.5 loops and forgot to resume the playback accidentally. Keep in mind that I listen to those loops during my sleep. If I pause the playback, It is if I have go to the bathroom in the middle of night when I'm not 100% conscious...
I did realize the glitch when I was about to launch day #6 loops playback. So I completed day#5 loops followed by the day #6 6 loops. For a total of 8.5 loops on day 6. I guess that in the long run, things will even up...
My heap corruption investigation did lead to a very productive bug hunt. With the closer inspection, I did find another bug and another improvement opportunity.
If I add the JSON decoding improvement, that starts to be a lot of fixes and improvements...
I also completed my new test program that does reproduce the events that did lead to the crash... I did use an incremental approach... I was adding 1 step to it. Then I was running it to make sure that I got the exact same result than what I am seeing the server log then I was continuing by adding the next step. Everything was smooth and I kinda lost hope to be able to reproduce the problem. Until, I added the very last step that did happen before the crash...
And my test program did crash... I haven't started to analyze the test program crash but it feels like it is very promising. I may eliminate a serious bug that is triggered only in very specific conditions that I haven't understood yet...
This is so cool...
