<https://line6.com/support/topic/53482-serious-helix-282-bug-christmas-researchupdated/#comment-320675>
<http://schema.org/text>
"Another update .....\n \n\n\n\t \n \n\n\n\tThe lower path of Path A was failing regardless of whether any effects in that lower path were on, or what splits were being used. As soon as I moved those effects to a different location, or deleted them (either option eliminated the path) the signal came back to full strength. Even when I simply tried using the split to re-route to the top path it would not bring the track to life... that lower path had to be eliminated. Of course, reloading the preset always brought it to life, but I was trying to avoid that for troubleshooting the dead preset. \n \n\n\n\t \n \n\n\n\tIn all three tests I did it took more than 3 hours for this to happen. I also checked every resource I could on my system, and memory was NOT an issue, so I don't believe this is a memory leak. CPU usage also remained consistent when the problem occurred so that eliminates resources. \n \n\n\n\t \n \n\n\n\tMy next test.\n \n\n\n\tI run a mega serial path for my live presets which utilize Path A in a similar way your preset was setup... except mine has even more added. I just loaded that up in Native to see if this problem happens with my preset. It will take several hours before I know. \n \n\n\n\t \n \n"
<https://line6.com/support/topic/53482-serious-helix-282-bug-christmas-researchupdated/#comment-320704>