Search Issue Tracker

Fixed in 2018.1

Not Reproducible in 5.6

Fixed in 2017.3

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 (15)

  1. 20dd0c6d1127a324db8bea2b1eca2467?d=mm

    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.

  2. Dbe35a0eb8eec5f729f5c753707aa34f?d=mm

    Karbec

    Aug 24, 2018 10:03

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

  3. Dbe35a0eb8eec5f729f5c753707aa34f?d=mm

    Karbec

    Aug 24, 2018 10:02

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

  4. Dbe35a0eb8eec5f729f5c753707aa34f?d=mm

    Karbec

    Aug 24, 2018 09:57

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

  5. Ea807b21d9e145d082cac463563fd402?d=mm

    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.

  6. Efb7db6ec251a3c7acf3665270988a7a?d=mm

    Nick62

    Mar 29, 2018 15:40

    I am also getting it with Unity 2017.3.1p1

  7. 14ccbef68b8cae0cae67a3b969d168ce?d=mm

    Tim_Timoff

    Mar 26, 2018 08:03

    I am also getting it with Unity 2017.3.1

  8. C4ac3c10433c8c131d13c555173b02db?d=mm

    creativewax

    Mar 08, 2018 12:34

    Happens randomly for me, happen again today on 2017.3 when importing a project, without doing anything the error keeps getting logged to the console

  9. C1b1465779f40cbc170b640216b1a97d?d=mm

    fashrista

    Mar 03, 2018 15:01

    yeh I have the same isue and was directed to this thread by unity bug report staf ie this is a known error, but me being here does not exactly solve it, does it? ;D

    For me the issue started after inporting my project into new beta version. It goes away if I slear the console. Everything works for me afterwards....so.... I gues it is not aserious problem?

  10. 66e42487e079c40168f634a96fb46c73?d=mm

    Kill22pro

    Feb 27, 2018 08:37

    Same error, but maybe from a different cause.
    Unity 2017.3.1p1

    Assertion failed: Assertion failed on expression: 'm_CurrentEntriesPtr != NULL && m_IsGettingEntries'
    System.Runtime.CompulerServices.ExecutionScope:lambda_method(ExecutionScope, Object, Object[])
    FlyingWormConsole3.FastMethodInfo:Invoke(Object, Object[])
    FlyingWormConsole3.NativeLogs:RefreshEntries(Boolean, Boolean)
    FlyingWormConsole3.ConsolePro3Window:EditorUpdate()
    UnityEditor.EditorApplication:Internal_CallUpdateFunctions()

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.