Search Issue Tracker

Fixed in 2018.1.X

Not Reproducible in 5.6.X

Fixed in 2017.3.X

Votes

13

Found in

2017.1.0b5

Issue ID

909987

Regression

Yes

m_CurrentEntriesPtr != NULL && m_IsGettingEntries error thrown when double clicking on a specific warning

Themes

-

To reproduce:

1. Open the project, attached by user (WrongCursor.zip)
2. Enter and exit Play mode. Warning "Invalid texture used for cursor - check importer settings" should be shown
3. Double click on warning
4. Observe console

Expected: double clicking on warning does not throw any errors
Actual: "Assertion failed: Assertion failed on expression: 'm_CurrentEntriesPtr != NULL && m_IsGettingEntries' error is thrown after double clicking on specific warning

Reproduced in 5.5.3.p2, 5.6.1f1, 2017.1.0b5

Regression introduced by this changeset: 63394166f856

Comments (19)

  1. wechat_os_Qy0zJ-Znecq6-vN3lgA5aklU4_unity

    Mar 02, 2022 11:12

    Same ERROR in 2021.2.12f1
    wtf unity

  2. YaroslavSm

    Dec 02, 2020 12:14

    2019.4 still here, F*** UNITY

  3. cwennchen

    Mar 30, 2020 02:54

    Same error, in Unity2018.3.8f1

  4. cwbeta

    Dec 26, 2019 04:48

    Same error in Unity 2017.3.1f1
    The console keeps typing this error and freezes unity even when the game is not running.

  5. ohbado

    Sep 17, 2018 01:55

    This error message was also displayed on Unity 2017.4.11f1. This error message was not displayed until 2017.4.10.

  6. Karbec

    Aug 24, 2018 10:03

    Still present in 2018.2.2f1. It happens when you try to clear console which contains errors.

  7. Karbec

    Aug 24, 2018 10:02

    Still present in 2018.2.2f1. It happens when you try to clear console containing errors

  8. Karbec

    Aug 24, 2018 09:57

    Still present in 2018.2.2f1. It happens when you try to clear console containing errors

  9. pjbaron

    Apr 16, 2018 23:33

    FYI: I had the same problem in Unity 2017_4_0 after merging the Xsolla Unity SDK with an existing project. It was resolved by a re-import of all assets.

  10. Nick62

    Mar 29, 2018 15:40

    I am also getting it with Unity 2017.3.1p1

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.