-
Notifications
You must be signed in to change notification settings - Fork 11
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
How to deal with "Evaluation timed out" problem? #62
Comments
As a temporary workaround, you can increase the timeout length; see https://stackoverflow.com/q/787334/111794. AFAICT with a large tree, the visualizer processes the entire tree, even when the user can only see a fraction of the tree at once. The solution would be to only process part of the tree, and be able to request other parts on demand. |
@zspitz I tried. It doesn't works. I'm using Visual Studio 2019. |
The configuration may be stored in a different place in VS 2019 -- https://stackoverflow.com/questions/41119996/where-does-visual-studio-2017-store-its-config?noredirect=1&lq=1 . |
[VS2019] In my case I have a fairly sample grammar and I've seen the error the first time I've tried visualizer on an string. And the error persisted until I restarted VS. Now it works fine. |
@MihaMarkic Do you think you could attach the grammar and string to this issue? @doggy8088 I assume this isn't what you're seeing; you're seeing the same error multiple times, even after having restarted VS. Could you attach a grammar and sample string? |
@zspitz My original grammar quality is pretty low. After rewriting my grammar, all performance issue has been resolved. |
@zspitz It was really a simple one taken from tutorial, I think. It most probably isn't important in this case. I've overwritten it since I posted. But if I see the same error again, I'll post the grammar here. |
@doggy8088 @MihaMarkic Thanks to you both for reporting and interacting on this issue. It's still a relevant problem, when there's a large parse tree. But I'm going to hold off on this for now, because fixing it is a significant architectural change. |
If my source too big, how can I still show the ANTLR4 Parse Tree Visualizer?
The text was updated successfully, but these errors were encountered: