-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
radar chart crash #882
Comments
Any reproducible code? |
Having the same issue when all RadarEntry have the same value. |
I'm able to reproduce the issue with the following code:
|
Found an infinite loop
I'll start working on a fix and submit a pull request as soon as I can |
ateich
added a commit
to ateich/fl_chart
that referenced
this issue
Jun 30, 2022
If the max and min values in a RadarDataSet are equal, the `drawTicks` method in `radar_chart_painter.dart` will enter an infinite loop. This is due to a for loop that fails to be incremented if the max and min values are equal, causing the loop to never meet its exit condition. I have replaced the for loop with one that will always exit. Resolves imaNNeo#882
imaNNeo
pushed a commit
that referenced
this issue
Jul 1, 2022
If the max and min values in a RadarDataSet are equal, the `drawTicks` method in `radar_chart_painter.dart` will enter an infinite loop. This is due to a for loop that fails to be incremented if the max and min values are equal, causing the loop to never meet its exit condition. I have replaced the for loop with one that will always exit. Resolves #882
Hi, I have the same problem too. |
Merged
Fixed in 0.55.1. Check it out! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
fl_chart 4.1.0 if you got one RawDataSet and values are same.
E/DartVM ( 5843): Exhausted heap space, trying to allocate 268435464 bytes.
════════ Exception caught by rendering library ═════════════════════════════════
The following OutOfMemoryError was thrown during paint():
Out of Memory
radarchart sample code
The text was updated successfully, but these errors were encountered: