Search Issue Tracker

Fixed

Fixed in 2.8.1

Votes

0

Found in [Package]

2.8.0

Issue ID

SPLB-353

Regression

Yes

DisposeNativeSplinesCache() call throws exceptions when entering Play mode with attached debugger due to null m_NativeSplinesCache

Package: Splines

-

Reproduction steps:
1. Open the attached “IN-98869.zip” project
2. Open the “SampleScene”
3. Open an external debugger (e.g. JetBrains Rider)
4. Attach it to Unity Editor
5. In the Editor, enter Play mode
6. Observe the debugger

Expected result: No exceptions are thrown
Actual result: “System.NullReferenceException: Object reference not set to an instance of an object at UnityEngine.Splines.SplineContainer.DisposeNativeSplinesCache” exception is thrown

Reproducible with: 2.8.0 (2022.3.61f1, 6000.0.46f1, 6000.1.0b14, 6000.2.0a8)
Not reproducible with: 2.7.2 (2022.3.61f1, 6000.0.46f1, 6000.1.0b14, 6000.2.0a8)

Reproducible on: Windows 11
Not reproducible on: No other environment tested

  1. Resolution Note:

    Fixed by another internal issue: SPLB-345: Tests failing - IL2CPP builds that include splines are failing on spline disposal

  2. Resolution Note (fix version 2.8.1):

    Fixed by another internal issue: SPLB-345: Tests failing - IL2CPP builds that include splines are failing on spline disposal

Log in to vote on this issue

Comments (5)

  1. SupinePandora43

    Jun 02, 2025 14:19

    I have this problem with Cinemachine 3.1.3

  2. kundara

    Apr 29, 2025 09:56

    It's amazing, that this spline package proves every time it's not ready to production. It's been in development for so long, and you still better trust some spline editors from the asset stores.

    Is it really that hard?

  3. kundara

    Apr 29, 2025 09:35

    What's up guys??
    Not nice to see nulls entering my game with "Wont fix".

    Please clarify

  4. dlich

    Apr 29, 2025 06:06

    Yeah, I'd really like to know what's going on with this issue and when to expect a fix.

  5. Claytonious

    Apr 17, 2025 14:37

    > This issue was identified and logged internally and has now been fixed for the next upcoming release.

    BUT that "internally logged" issue is not visible to the public, and you've marked this one as "Won't Fix" - so we cannot see anything useful now:

    * Which "upcoming next release" are you talking about? The splines package or Unity?
    * Which specific version number are you saying it's fixed in?

    These details are usually provided above but since you marked this "WON'T FIX" instead of providing those this has become opaque and useless.

    Shouldn't this be "duplicate" or something but still with all of those details above?

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.

Latest issues

See all new issues