-
Notifications
You must be signed in to change notification settings - Fork 541
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[.NET Renderer][Performance] Calling Visit on AdaptiveVisitor and passing in an AdaptiveToggleVisibilityAction causes an infinite loop. #4164
Comments
Hi @DDEfromOR; We triaged and approved your bug for fixing. Please stay tuned for updates around fix progress and/or release vehicle. |
Hi @DDEfromOR. We have acknowledged this issue report. Please continue to follow this issue for updates/progress/questions. |
@jwoo-msft please prioritize. tx |
@shalinijoshi19 This is not a templating issue. It's .Net Rendering issue. |
@DDEfromOR Can you share your payload that caused this issue? Thanks |
* wip * almost fixed * work in progress * Fixed issue #4164 * Updated ANTLR to 4.8 and brought up AEL version * updated parser & lexer * removed a dangling line.
* Fixed issue #4164 * design spec for whitespace handling update for markdown * Updated the spec * a few minor detail added
* Fixed issue #4164 * [.NET][Template] Fixed ANTLR version mismatch
* Fixed issue #4164 * [.NET][Template] Fixed ANTLR version mismatch
* Fixed issue #4164 * [dotnet] Added Simple Memory Interface * fixed the typo for comments
* Fixed issue #4164 * [dotnet] Added Simple Memory Interface * fixed the typo for comments
Platform
What platform is your issue or question related to? (Delete other platforms).
Author or host
We are a service that supports sending Adaptive Cards between various chat clients and Azure Bots.
Version of SDK
NuGet: AdaptiveCards v1.2.4
Details
An analysis of crash dumps from a series of high CPU usage issues revealed an infinite loop that seems to be initiated by by calling the Visit(AdaptiveAction) function on AdaptiveVisitor when passing in an AdaptiveToggleVisibilityAction. Specifically the call on line 142 attempts to find an overload of Visit that accepts an AdaptiveToggleVisibilityAction, fails as no such overload exists, and instead matches with itself, as AdaptiveToggleVisibilityAction derives from AdaptiveAction. It looks like the other paths in this logic have sub-type specific overloads of Visit and this one was simply missed.
The text was updated successfully, but these errors were encountered: