BUG: Z.Blazor.Diagram crashes (whole application) when you are scrolling too much or too long
See original GitHub issueSteps to reproduce:
- scroll, a lot
- Tested on big canvas and is much more likely to crash
- on canvases with not as much nodes it is harder it triggers when there are nodes not visible inside the div/view.
Module._mono_wasm_invoke_method@https://blazor-diagrams.zhaytam.com/_framework/wasm/dotnet.3.2.0.js:1:195738 [blazor.webassembly.js:1:37761](https://blazor-diagrams.zhaytam.com/_framework/blazor.webassembly.js)
call_method@https://blazor-diagrams.zhaytam.com/_framework/wasm/dotnet.3.2.0.js:1:160823 [blazor.webassembly.js:1:37761](https://blazor-diagrams.zhaytam.com/_framework/blazor.webassembly.js)
bind_static_method/<@https://blazor-diagrams.zhaytam.com/_framework/wasm/dotnet.3.2.0.js:1:163094 [blazor.webassembly.js:1:37761](https://blazor-diagrams.zhaytam.com/_framework/blazor.webassembly.js)
beginInvokeDotNetFromJS@https://blazor-diagrams.zhaytam.com/_framework/blazor.webassembly.js:1:41357 [blazor.webassembly.js:1:37761](https://blazor-diagrams.zhaytam.com/_framework/blazor.webassembly.js)
s@https://blazor-diagrams.zhaytam.com/_framework/blazor.webassembly.js:1:8562 [blazor.webassembly.js:1:37761](https://blazor-diagrams.zhaytam.com/_framework/blazor.webassembly.js)
e.invokeMethodAsync@https://blazor-diagrams.zhaytam.com/_framework/blazor.webassembly.js:1:9641 [blazor.webassembly.js:1:37761](https://blazor-diagrams.zhaytam.com/_framework/blazor.webassembly.js)
v/</</<@https://blazor-diagrams.zhaytam.com/_framework/blazor.webassembly.js:1:34635 [blazor.webassembly.js:1:37761](https://blazor-diagrams.zhaytam.com/_framework/blazor.webassembly.js)
t.dispatchEvent@https://blazor-diagrams.zhaytam.com/_framework/blazor.webassembly.js:1:11187 [blazor.webassembly.js:1:37761](https://blazor-diagrams.zhaytam.com/_framework/blazor.webassembly.js)
e/this.eventDelegator</<@https://blazor-diagrams.zhaytam.com/_framework/blazor.webassembly.js:1:12101 [blazor.webassembly.js:1:37761](https://blazor-diagrams.zhaytam.com/_framework/blazor.webassembly.js)
e/this.eventDelegator<@https://blazor-diagrams.zhaytam.com/_framework/blazor.webassembly.js:1:12125 [blazor.webassembly.js:1:37761](https://blazor-diagrams.zhaytam.com/_framework/blazor.webassembly.js)
e.prototype.onGlobalEvent@https://blazor-diagrams.zhaytam.com/_framework/blazor.webassembly.js:1:22181 [blazor.webassembly.js:1:37761](https://blazor-diagrams.zhaytam.com/_framework/blazor.webassembly.js)
<empty string> [blazor.webassembly.js:1:37761](https://blazor-diagrams.zhaytam.com/_framework/blazor.webassembly.js)
at System.Threading.Tasks.ValueTask`1[TResult].get_Result () <0x21b37f0 + 0x0002c> in <filename unknown>:0 [blazor.webassembly.js:1:37761](https://blazor-diagrams.zhaytam.com/_framework/blazor.webassembly.js)
at Microsoft.JSInterop.JSRuntimeExtensions.InvokeVoidAsync (Microsoft.JSInterop.IJSRuntime jsRuntime, System.String identifier, System.Object[] args) <0x2135260 + 0x000e4> in <filename unknown>:0 [blazor.webassembly.js:1:37761](https://blazor-diagrams.zhaytam.com/_framework/blazor.webassembly.js)
at Blazor.Diagrams.Extensions.JSRuntimeExtensions.UnobserveResizes (Microsoft.JSInterop.IJSRuntime jsRuntime, Microsoft.AspNetCore.Components.ElementReference element) <0x244b6d0 + 0x000ee> in <filename unknown>:0 [blazor.webassembly.js:1:37761](https://blazor-diagrams.zhaytam.com/_framework/blazor.webassembly.js)
at Blazor.Diagrams.Components.Renderers.NodeRenderer.CheckVisibility () <0x22e7f28 + 0x00292> in <filename unknown>:0 [blazor.webassembly.js:1:37761](https://blazor-diagrams.zhaytam.com/_framework/blazor.webassembly.js)
at System.Runtime.CompilerServices.AsyncMethodBuilderCore+<>c.<ThrowAsync>b__7_1 (System.Object state) <0x25f8fd8 + 0x0000c> in <filename unknown>:0 [blazor.webassembly.js:1:37761](https://blazor-diagrams.zhaytam.com/_framework/blazor.webassembly.js)
at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context (System.Object state) <0x25f8f88 + 0x0001c> in <filename unknown>:0 [blazor.webassembly.js:1:37761](https://blazor-diagrams.zhaytam.com/_framework/blazor.webassembly.js)
at System.Threading.ExecutionContext.RunInternal (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) <0x1bad018 + 0x00100> in <filename unknown>:0 [blazor.webassembly.js:1:37761](https://blazor-diagrams.zhaytam.com/_framework/blazor.webassembly.js)
at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) <0x1bacdd8 + 0x00010> in <filename unknown>:0 [blazor.webassembly.js:1:37761](https://blazor-diagrams.zhaytam.com/_framework/blazor.webassembly.js)
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem () <0x25f8f18 + 0x00038> in <filename unknown>:0 [blazor.webassembly.js:1:37761](https://blazor-diagrams.zhaytam.com/_framework/blazor.webassembly.js)
at System.Threading.ThreadPoolWorkQueue.Dispatch () <0x22a1460 + 0x00102> in <filename unknown>:0 [blazor.webassembly.js:1:37761](https://blazor-diagrams.zhaytam.com/_framework/blazor.webassembly.js)
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback () <0x22a10c8 + 0x00000> in <filename unknown>:0 [blazor.webassembly.js:1:37761](https://blazor-diagrams.zhaytam.com/_framework/blazor.webassembly.js)
Uncaught
Object { name: "ExitStatus", message: "Program terminated with exit(255)", status: 255 }
Issue Analytics
- State:
- Created 10 months ago
- Comments:6
Top Results From Across the Web
Issues · Blazor-Diagrams/Blazor.Diagrams
Trying to prevent a user to remove a node using an async pattern ... Diagram crashes (whole application) when you are scrolling too...
Read more >Blazor app crashes when debugging after windows ...
Anytime I would run the program with breakpoints in my code it would crash. Removing all breakpoints before running seems to work as...
Read more >vs 2022 17.0.3: blazor server project: is running low ...
Using our production blazor server project after making code changes the background task start running, my CPU fan starts spinning, and the error...
Read more >How to show organization chart with Z.Blazor.Diagrams ...
I solved it by saving position in database. On every node movement point(x,y) changes so I create the chart in the shape that...
Read more >Untitled
Kara remembers episode, It's been such a long time, How far i'll go chord no capo, Curtains for different sized windows in same...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Most likely the beginning of december.
@zHaytam Do you have any predictions of when version 3.0 will come out of beta?