ID 584303 - Particles with random start frames can freeze unexpectedly when the input media is set to "bounce" or "loop" and max_clip_length exceeds its duration

Particles with random start frames can freeze unexpectedly when the input media is set to "bounce" or "loop" and max_clip_length exceeds its duration
 
Customer reported version:
Nuke N/A
 
Customer reported platform:
macOS 
 
Steps to reproduce:
1) Download the attached particle_freeze_demo.nk Nuke script and launch NukeX
2) Scrub through the timeline and observe how some particles will freeze when reaching a certain frame, in this case 2092:

 
Expected behavior:
Particles should not freeze and hold seemingly arbitrary frames for the remainder of their lifespan.
 
Actual behavior:
If a ParticleEmitter is creating particles with random start frames (start_frame_animation knob set to "random"), setting the max_clip_length knob to a value larger than an input image sequence's duration can cause particles to freeze and hold a single frame until the end of the particle's life.
 
This only seems to occur if the input media is set to "bounce" or "loop" from the Read node's after knob (or from the after knob of a Retime/TimeClip/etc.). If the input is set to "hold" instead, then the particle will freeze when it reaches the last frame of the input sequence, which is expected.
 
Workaround:
No known workaround at this time.
 
Reproduced by Support in:
NukeX 15.1v2 - Windows 10, macOS 14 Sonoma
NukeX 14.0v1 - Windows 10
NukeX 12.0v1 - Windows 10
 
Earliest version tested:
NukeX 12.0v1 - This issue appears to be in all tested versions of the product