-
-
Notifications
You must be signed in to change notification settings - Fork 7.9k
y limit with dashed or dotted lines hangs with somewhat big data #1758
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
Comments
Thanks @fmder. Can you let us know which backend your using?:
Cheers, |
>>> print matplotlib.rcParams['backend']
MacOSX |
@fmder Is this still a problem on newer version of mpl? (I don't have a mac set up to test this) |
I can still reproduce this with today's @mdehoon: Any thoughts? |
I've seen this before with Quartz. I believe the problem is that when In this case with the exponential data set and the limits set as so, the lines in terms of pixels are insanely big and I bet the time for Quartz to finish would be something completely absurd. |
It's indeed CGContextStrokePath that is taking forever to finish. path = Path([[ 0.00000000e+00 1.00000000e+00] transform = Affine2D(array([[ 9.92, 0. , 80. ], This suggests that we are trying to draw the full line instead of just the section that will be visible in the window. Perhaps the calling function (_ draw_dashed in matplotlib/lines.py, called as part of the draw method of Line2D) should only draw the section of the line that will be visible, rather than the whole thing? Currently it seems to rely on clipping in order to show the visible section only. |
Closed by #6178. |
When plotting uncontinuous lines and rescaling the y axis to centre the view on some part of the data matplotlib hangs in the show() function forcing me to kill the process.
How to reproduce the bug:
This does work perfectly with a continuous line or when the data is smaller and uncontinuous lines.
I use matplotlib 1.2.0 on OSX 10.7.5 and I have Python 2.7.3 installed as a famework (with homebrew).
The text was updated successfully, but these errors were encountered: