Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. Join us on Thursday, June 8, for a Q&A with Unity's Content Pipeline group here on the forum, and on the Unity Discord, and discuss topics around Content Build, Import Workflows, Asset Database, and Addressables!
    Dismiss Notice
New Forum User Notice Content Pipeline Dev Blitz Day

[...or UI?] NullReferenceException with no stack trace, with Stack Trace Logging>Full

Discussion in '5.3 Beta' started by chrismarch, Dec 3, 2015.

  1. chrismarch

    chrismarch

    Joined:
    Jul 24, 2013
    Posts:
    459
    I'm seeing this error in the 5.3.0f2 editor and Windows standalone builds, and clicking instances of this error in the Console window highlights UI objects in the Hierarchy that contain all of these: Animator, Text (deactivated), Outline and Canvas Renderer components (and RectTransforms, and one custom script that checks for null references before dereferencing). Even with Stack Trace Logging>Full there is no additional info in the bottom of the console when I click the error. Warnings above it are from other objects, so I don't have much to go on.
     
    Last edited: Dec 3, 2015
    chrismarch, Dec 3, 2015
    #1

  2. chrismarch

    chrismarch

    Joined:
    Jul 24, 2013
    Posts:
    459
    Is anyone getting stack traces from errors or exceptions originating in Unity code (not your own scripts) with Stack Trace Logging>Script Only?
     
    chrismarch, Dec 4, 2015
    #2

  3. chrismarch

    chrismarch

    Joined:
    Jul 24, 2013
    Posts:
    459
    The exception appears to be coming after calls to Animator.Play on a controller that has a valid Motion to play on a UI object with a Text component
     

    Attached Files:

    • clip.png
      clip.png
      File size:
      28.4 KB
      Views:
      1,048
    chrismarch, Dec 4, 2015
    #3

  4. chrismarch

    chrismarch

    Joined:
    Jul 24, 2013
    Posts:
    459
    the exception may be fixed in coming builds, but I'd still like to know why there was no stack trace
     
    chrismarch, Dec 4, 2015
    #4