Jump to content

Crash with "report error"

Gurgel

By Gurgel

    • Branch: Preview Branch Version: Windows Fixed

I have now several times gotten a crash that when clicking the report button also gives a "report error". Date collection is enabled. Trace below:

Assert failed

  at UnityEngine.Debug.LogError (System.Object message) [0x00000] in <9fe2cbebfa394c8da6af069ec8cc9ef4>:0 
  at Debug.LogError (System.Object obj) [0x00000] in <8e85aab05d1d44a5b339d82e5aea3b88>:0 
  at Debug.Assert (System.Boolean condition) [0x00000] in <8e85aab05d1d44a5b339d82e5aea3b88>:0 
  at HandleVector`1[T].PackHandle (System.Int32 index) [0x00000] in <8e85aab05d1d44a5b339d82e5aea3b88>:0 
  at HandleVector`1[T].Add (T item) [0x00000] in <8e85aab05d1d44a5b339d82e5aea3b88>:0 
  at KCompactedVectorBase.Allocate (System.Int32 item) [0x00000] in <8e85aab05d1d44a5b339d82e5aea3b88>:0 
  at KCompactedVector`1[T].Allocate (T initial_data) [0x00000] in <8e85aab05d1d44a5b339d82e5aea3b88>:0 
  at AnimEventManager.PlayAnim (KAnimControllerBase controller, KAnim+Anim anim, KAnim+PlayMode mode, System.Single time, System.Boolean use_unscaled_time) [0x00000] in <c8af1c7577924b4e8159a8d1b7565399>:0 
  at KAnimControllerBase.StartAnimEventSequence () [0x00000] in <c8af1c7577924b4e8159a8d1b7565399>:0 
  at KAnimControllerBase.StartQueuedAnim () [0x00000] in <c8af1c7577924b4e8159a8d1b7565399>:0 
  at KAnimControllerBase.Queue (HashedString anim_name, KAnim+PlayMode mode, System.Single speed, System.Single time_offset) [0x00000] in <c8af1c7577924b4e8159a8d1b7565399>:0 
  at KAnimControllerBase.Play (HashedString anim_name, KAnim+PlayMode mode, System.Single speed, System.Single time_offset) [0x00000] in <c8af1c7577924b4e8159a8d1b7565399>:0 
  at TransitionDriver.BeginTransition (Navigator navigator, Navigator+ActiveTransition transition) [0x00000] in <c8af1c7577924b4e8159a8d1b7565399>:0 
  at Navigator.BeginTransition (NavGrid+Transition transition) [0x00000] in <c8af1c7577924b4e8159a8d1b7565399>:0 
  at Navigator.AdvancePath (System.Boolean trigger_advance) [0x00000] in <c8af1c7577924b4e8159a8d1b7565399>:0 
  at TransitionDriver.UpdateTransition (System.Single dt) [0x00000] in <c8af1c7577924b4e8159a8d1b7565399>:0 
  at Navigator.SimEveryTick (System.Single dt) [0x00000] in <c8af1c7577924b4e8159a8d1b7565399>:0 
  at Navigator+States+<>c.<InitializeStates>b__5_2 (Navigator+StatesInstance smi, System.Single dt) [0x00000] in <c8af1c7577924b4e8159a8d1b7565399>:0 
  at BucketUpdater`1[DataType].Update (DataType data, System.Single dt) [0x00000] in <8e85aab05d1d44a5b339d82e5aea3b88>:0 
  at UpdateBucketWithUpdater`1[DataType].Update (System.Single dt) [0x00000] in <8e85aab05d1d44a5b339d82e5aea3b88>:0 
  at StateMachineUpdater+BucketGroup.AdvanceOneSubTick (System.Single dt) [0x00000] in <8e85aab05d1d44a5b339d82e5aea3b88>:0 
  at StateMachineUpdater.AdvanceOneSimSubTick () [0x00000] in <8e85aab05d1d44a5b339d82e5aea3b88>:0 
  at Game.SimEveryTick (System.Single dt) [0x00000] in <c8af1c7577924b4e8159a8d1b7565399>:0 
  at Game.Update () [0x00000] in <c8af1c7577924b4e8159a8d1b7565399>:0 
Build: U37-484114-S

Steps to Reproduce

No idea. Seems to happen randomly after a few hours.

  • Haha 1
Go to bugs

User Feedback


A developer has marked this issue as fixed. This means that the issue has been addressed in the current development build and will likely be in the next update.
Gurgel

I got it again and I think this is was actually "reported error", which is not quite clear but seems to indicate the error actually got reported. If so, I would suggest changing the message to "Error was successfully reported" to make it clear.

Edited by Gurgel
  • Haha 2

Share this comment

Link to comment
Share on other sites
sakura_sk

You mean this fine message that confirms you "reported the error"? At least I think that's what it means... otherwise I've never sent a crash report properly :???:

crash.thumb.JPG.93f6a8db0bd976731272de8897497b20.JPG

  • Haha 2

Share this comment

Link to comment
Share on other sites
RuiPalhas
1 hour ago, sakura_sk said:

You mean this fine message that confirms you "reported the error"? At least I think that's what it means... otherwise I've never sent a crash report properly :???:

crash.thumb.JPG.93f6a8db0bd976731272de8897497b20.JPG

It looks like they swapped the word order :lol: "error reported" makes more sense

  • Like 1
  • Thanks 2

Share this comment

Link to comment
Share on other sites


Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...