Crashes when Clip parent is null

[jminor]

An LLM-based code review claims that there are some bugs related to orphaned clips (Clip instances with a null parent).

item.cpp:87-109 — range_in_parent/trimmed_range_in_parent on an orphan clip set the error then still call parent()->... on null. Same pattern in transition.cpp:58-90.
composition.cpp:254-273 — _path_from_child walks current->parent() off the end for orphan/foreign children: track->range_of_child(orphan) crashes.

Could we get a volunteer to verify if this is a real bug? It sounds plausible, and could be easily verified by writing a test case and/or a test OTIO file that creates the scenario described.

[Ultimatekirito]

Hi! I’m a student at USM interested in contributing to OpenTimelineIO for my semester-long software engineering project. This would be my first open-source contribution. I have experience with C++, though I’m refreshing my skills.

I’m interested in starting with issue #2042 and potentially working on #2044 and #2045 afterward. Are these available, and would they be reasonable starting points for a first-time contributor?

I’m balancing a full course load and work, so I want to keep my commitments manageable by working on one issue at a time. I’ll follow the contribution guidelines and address review feedback.

Thanks for your time!

[jminor]

Hi @Ultimatekirito, yes all of those are good tasks for a first time contributor. There is an opportunity for some mentorship this week via this event: https://www.aswf.io/dev-days/

[Ishubhammohole]

I would like to work on this now. I will first reproduce the orphan/null-parent paths in regression tests, then keep the C++ fix limited to the confirmed null-safe behavior and run the affected C++/Python tests.