Sporadic exception invoking 'RadzenTooltip.CloseTooltip' #1544

Closed
opened 2026-01-29 17:55:11 +00:00 by claunia · 0 comments
Owner

Originally created by @ax-meyer on GitHub (Dec 20, 2024).

Describe the bug
The error There was an exception invoking 'RadzenTooltip.CloseTooltip'. For more details turn on detailed exceptions in 'CircuitOptions.DetailedErrors' is thrown unhandled sporadically.

After upgrading from 5.5.4 to 5.7.0 4 days ago, we see this error a few times a day in a small app with < 10 users.

Full stack strace:

Error: There was an exception invoking 'RadzenTooltip.CloseTooltip'. For more details turn on detailed exceptions in 'CircuitOptions.DetailedErrors'
  at y.endInvokeDotNetFromJS(/_framework/blazor.web.js:1:3502)
  at fn._invokeClientMethod(/_framework/blazor.web.js:1:62914)
  at fn._processIncomingData(/_framework/blazor.web.js:1:60389)
  at connection.onreceive(/_framework/blazor.web.js:1:54030)
  at i.onmessage(/_framework/blazor.web.js:1:82175)

To Reproduce
I have sadly not been able to reproduce the error rebliably yet, especially not with DetailedErrors enabled. Happens sometimes when a tooltip closes. Will update when I get a better reproduction.

Expected behavior
Tooltip should close without error

Desktop (please complete the following information):

  • OS: Windows
  • Browser Firefox, Edge
  • Version Firefox 133, Edge 131

Additional context
The only change in the tooltip close behavior between 5.5.4 and 5.7.0 I can see is in this commit:
a0f1545421 (diff-5b58e94bbc18e5cb097acf4a1085e47988b70cc0cd02ea6d7ac2911594883e4aL87)

Specifically, I am wondering if the Enum-Parsing in line 102 might fail because a bad position string might be provided to the function at some point. That's the best guess I have to what changed and might cause a crash.

Originally created by @ax-meyer on GitHub (Dec 20, 2024). **Describe the bug** The error `There was an exception invoking 'RadzenTooltip.CloseTooltip'. For more details turn on detailed exceptions in 'CircuitOptions.DetailedErrors'` is thrown unhandled sporadically. After upgrading from 5.5.4 to 5.7.0 4 days ago, we see this error a few times a day in a small app with < 10 users. Full stack strace: ``` Error: There was an exception invoking 'RadzenTooltip.CloseTooltip'. For more details turn on detailed exceptions in 'CircuitOptions.DetailedErrors' at y.endInvokeDotNetFromJS(/_framework/blazor.web.js:1:3502) at fn._invokeClientMethod(/_framework/blazor.web.js:1:62914) at fn._processIncomingData(/_framework/blazor.web.js:1:60389) at connection.onreceive(/_framework/blazor.web.js:1:54030) at i.onmessage(/_framework/blazor.web.js:1:82175) ``` **To Reproduce** I have sadly not been able to reproduce the error rebliably yet, especially not with `DetailedErrors` enabled. Happens sometimes when a tooltip closes. Will update when I get a better reproduction. **Expected behavior** Tooltip should close without error **Desktop (please complete the following information):** - OS: Windows - Browser Firefox, Edge - Version Firefox 133, Edge 131 **Additional context** The only change in the tooltip close behavior between 5.5.4 and 5.7.0 I can see is in this commit: https://github.com/radzenhq/radzen-blazor/commit/a0f1545421ca2d6a00248840de6be33d506f288f#diff-5b58e94bbc18e5cb097acf4a1085e47988b70cc0cd02ea6d7ac2911594883e4aL87 Specifically, I am wondering if the Enum-Parsing in line 102 might fail because a bad position string might be provided to the function at some point. That's the best guess I have to what changed and might cause a crash.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/radzen-blazor#1544