Hello all!
On Windows 11, with a Segger Ultra+ debugger, we opened a timeline and sampled 3 variables. When we set the sample rate to max, Ozone hangs for about a minute and becomes unresponsive. We click pause, ozone continues to hang, eventually services the click, and returns to normal function.
This happened on multiple computers.
It seems that this behavior is triggered by how the timeline variables are referenced. If we select the desired variables via a global reference, the timeline functions as normal. However, when we tried to reference the vars through a singleton interface, the timeline became unresponsive. We suspect the timeline was re-parsing the singleton-reference every sample, causing the delay.
ex.
singleton::instance.struct.var (hangs)
vs.
pre-stored-pointer-to-instance.struct.var (functions as expected)
TY in advance!
On Windows 11, with a Segger Ultra+ debugger, we opened a timeline and sampled 3 variables. When we set the sample rate to max, Ozone hangs for about a minute and becomes unresponsive. We click pause, ozone continues to hang, eventually services the click, and returns to normal function.
This happened on multiple computers.
It seems that this behavior is triggered by how the timeline variables are referenced. If we select the desired variables via a global reference, the timeline functions as normal. However, when we tried to reference the vars through a singleton interface, the timeline became unresponsive. We suspect the timeline was re-parsing the singleton-reference every sample, causing the delay.
ex.
singleton::instance.struct.var (hangs)
vs.
pre-stored-pointer-to-instance.struct.var (functions as expected)
TY in advance!
