Summary: | Kmpot hangs on doing implicit plots with < or > sign in it. | ||
---|---|---|---|
Product: | [Applications] kmplot | Reporter: | Nikita Skovoroda <chalkerx> |
Component: | general | Assignee: | Klaus-Dieter M <kd.moeller> |
Status: | CONFIRMED --- | ||
Severity: | crash | CC: | eike.krumbacher, ewoerner, fraph24 |
Priority: | NOR | ||
Version: | 1.2.1 | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | kf5 port |
Description
Nikita Skovoroda
2007-12-15 13:53:42 UTC
kmplot from KDE 4.x simply doesn't draw this function, so it behaves right I guess. Of course an error message would be great. > kmplot from KDE 4.x simply doesn't draw this function, so it behaves right I guess.
Then it should give the user some sort of error message.
The problem is that it hangs and stops reacting to user actions.
Still hangs. chalker@linux:~> kmplot --version Qt: 4.5.0-snapshot-20080916 KDE: 4.1.66 (KDE 4.1.66 (KDE 4.2 >= 20080912)) "release 2.1" KmPlot: 1.2.0 Still hangs on „Qt: 4.5.2 KDE: 4.2.96 (KDE 4.2.96 (KDE 4.3 RC2)) KmPlot: 1.2.1“. No output to the console. The input indicator stops blinking, the window contents turn to blank (if kwin effects are off). „Qt: 4.6.3 KDE: 4.4.85 (KDE 4.4.85 (KDE 4.5 Beta2)) KmPlot: 1.2.1“ Using Arch Linux.(In reply to comment #5) > „Qt: 4.6.3 > KDE: 4.4.85 (KDE 4.4.85 (KDE 4.5 Beta2)) > KmPlot: 1.2.1“ Using Arch Linux and kde-unstable. The problem is still present. Qt: 4.7.3 KDE: 4.6.80 (4.7 Beta1) KmPlot: 1.2.1 Still hangs dead on (invalid?) input. Qt: 4.7.3 KDE: 4.7.41 (4.7.41 (KDE 4.8 >= 20110807) KmPlot: 1.2.1 Still hangs. And it builds wrong graph for: floor(x) = 1 y + floor(x) = 1 floor(y) = floor(x) — looks like junk Hi! Entering an equation like f(x) = x + y < 1 does not result in crash. You have to wait maybe 5 minutes. And then, you get the totally wrong result. If you like, you can test with g(x) = (x^2 + y^2) > 1, which goes faster. The result of the above equation (f) is a totally coloured/filled window, the latter (g) givese a figur which does not belong to the equation too. Eike Krumbacher, that's nice, it hanged on that before, too. Ok. Checked this again. Kmplot does not hang anymore, no «View::drawImplicitInSquare: Implicit: got to last iteration!» messages anymore. But the results are broken. Test functions: x*x + y*y < 1 floor(y) = floor(x) floor(x) = 1 y + floor(x) = 1 x + y < 1 (first example) — looks almost ok, but still not good enough. Whoops, i am mistaken here. There are still a lot of «View::drawImplicitInSquare: Implicit: got to last iteration!» messages. I just forgot to enable kdebugdialog. Sorry. x*x + y*y < 1 — still hangs with kmplot(2078) View::drawImplicitInSquare: Implicit: got to last iteration! … x*x + y*y > 1 — gives junk with kmplot(2078) View::drawImplicitInSquare: Implicit: got to last iteration! … kmplot(2078) View::drawImplicitInSquare: Implicit: got to last iteration! kmplot(2078) View::drawImplicitInSquare: Implicit: got to last iteration! kmplot(2078) View::drawImplicitInSquare: Couldn't find root - giving up. Tested on Qt: 4.8.0 KDE Development Platform: 4.7.97 (4.8 RC2 (4.7.97) KmPlot: 1.2.1 KDE: 4.8.3, Qt: 4.8.1, KmPlot: 1.2.1. Hangs. *** Bug 329556 has been marked as a duplicate of this bug. *** Created attachment 91574 [details]
kf5 port
KF: 5.8.0
Qt: 5.4.1
KmPlot: 1.2.1
Takes several minutes, but does not hang.
The result is not valid (see the attachment).
> Takes several minutes, but does not hang.
You should read that as «stops reacting for several minutes, then renders some strange result».
Trying to resize the window results in several more blocked minutes.
Thank you for the crash report. As it has been a while since this was reported, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved/worksforme" when you respond, thank you. Entering a simple relation such as 'x + y > 1' still causes a long lag, and a wrong result. |