 |
|
 |
I generated a new library that should fix the crash and shows an error message to help me identify the situation causing the crash: https://drive.google.com/file/d/1QlVb-4q8HVo6dLszDadg7ykmxZdbOCor/view?usp=sharing Please let me know if you get an error message like "Adding '<classname>' node to '<classname>' and parent is not connected to the View". |
|
|
Thanks -- I'm trying it out today. I'll report back. |
|
|
OK, I finally encountered it. [noesis] Adding 'Grid' node to 'Grid' and parent is not connected to the View UnityEngine.Debug:LogError (object) NoesisUnity:UnityLog (int,string) (at Assets/NoesisGUI/Plugins/NoesisUnity.cs:148) Noesis.View:Update (double) (at Assets/NoesisGUI/Plugins/API/Core/View.cs:333) NoesisView:ExternalUpdateInternal () (at Assets/NoesisGUI/Plugins/NoesisView.cs:910) NoesisView:LateUpdate () (at Assets/NoesisGUI/Plugins/NoesisView.cs:880) No crashes. |
|
|
Have you identified how to reproduce it? I was expecting different types involved and I'm still not sure what is the source of this situation. |
|
|
It may be related to a race condition in my code. I know what I was doing when I first saw it (thanks for the output) but I'm not sure if it is consistently reproducible, or where in the visual tree / code-behind it occurs. I'll keep looking today and reply back with more detail as I learn more. |
|
|
I came across a scenario the other day that consistently crashed Noesis. I believe I had mistakenly added a rectangle to a grid twice in a row -- a cut and paste error. I intended to return back to it and file a report but I was under a deadline to get things working. I am going to upgrade to 3.1.x today -- how do we want to proceed with this bug/behavior? |
|
|
Were you using the patched library I sent you? All those crashes are probably different from the one that started this ticket, can you attach the new crash dumps? |
|
|
Different crash on 3.0.12. |
|
|
Both crashes, first and second, happened using the patched library. |
|
|
Here is another one -- likely the same crash behavior as the second and most recent reported crash. These crashes are repeatable and they happen at runtime (not during app domain load/unload). I am testing space battles with large numbers of ships which have corresponding targeting UI framework elements. Noesis is stable with 100+ targets with position and blend updating once per frame. However, once I enable the ability for ships to be destroyed -- which also destroys targeting reticles, I find that I get crashes in a few seconds of each battle starting. The UI which displays these targets is long-lived and is never destroyed. The UI elements are added and removed from a Canvas. The control which contains the canvas implements OnRendering via the following syntax: private void InitializeComponent() { Loaded += (sender, e) => { _View = View; _View.Rendering += OnRendering; }; Unloaded += (sender, e) => { _View.Rendering -= OnRendering; _View = null; }; GUI.LoadComponent(this, "Assets/User Interface/Screens/Game/Overlay/Targeting/TargetingControl.xaml"); _Root = this.Content as FrameworkElement; _Canvas = _Root.FindName("_Canvas") as Canvas; } I hope this information is helpful. Thank you! |
|
|
|
|
|
Below: Possibly the same crash as reported on 10/27 but the stack trace is different and the error is associated with d3d11.dll. |
|
|
|
- Anonymous
