Bug 187686 - The step program can be hanged trivially
Summary: The step program can be hanged trivially
Status: RESOLVED WORKSFORME
Alias: None
Product: step
Classification: Applications
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Sebastian Ziebarth
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-20 09:41 UTC by Alex Riesen
Modified: 2020-12-28 23:50 UTC (History)
6 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
attachment-25814-0.html (1.79 KB, text/html)
2020-12-04 06:21 UTC, Alex Riesen
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alex Riesen 2009-03-20 09:41:33 UTC
Version:            (using KDE 4.2.0)
OS:                Linux
Installed from:    Ubuntu Packages

Ubuntu Bug: https://bugs.launchpad.net/ubuntu/+source/kdeedu/+bug/333528

Happens most frequently after this "steps":
- create a point
- pin it to the world with an anchor
- and try to add a stick starting at the point: click on the point and release the mouse button
  (sometimes stick can be added, but an attempt to modify it will hang the program). Very short stick, yes.

The program hangs going into endless loop:

(gdb) bt
#0 0x00000000004a685f in gmm::constrained_cg<gmm::row_matrix<gmm::rsvector<double> >, gmm::row_matrix<gmm::rsvector<double> >, gmm::identity_matrix, std::vector<double, std::allocator<double> >, std::vector<double, std::allocator<double> >, std::vector<double, std::allocator<double> >, gmm::identity_matrix> (A=@0x7fff37921490, C=@0x7fff37921430, x=@0x7fff379214f0, b=@0x7fff37921510, f=@0x7fff379214d0, PS=@0x7fff3792157f, M=@0x7fff3792157e, iter=@0x7fff379213d0) at /usr/include/gmm/gmm_blas.h:1665
#1 0x00000000004a31a3 in StepCore::CGConstraintSolver::solve (this=<value optimized out>, info=0x1efcdb8) at /build/buildd/kdeedu-4.1.4/step/stepcore/constraintsolver.cc:111
#2 0x0000000000497516 in StepCore::World::solverFunction (t=<value optimized out>, y=0x1f87d10, yvar=<value optimized out>, f=0x241ecc0, fvar=0x0, params=<value optimized out>) at /build/buildd/kdeedu-4.1.4/step/stepcore/world.cc:878
#3 0x0000000000431e51 in WorldModel::doEmitChanged (this=0x1ecf460) at /build/buildd/kdeedu-4.1.4/step/step/worldmodel.cc:396
#4 0x0000000000436a28 in WorldModel::qt_metacall (this=0x1ecf460, _c=QMetaObject::InvokeMetaMethod, _id=3, _a=0x7fff37921700) at /build/buildd/kdeedu-4.1.4/obj-x86_64-linux-gnu/step/step/worldmodel.moc:85
#5 0x00007f2e2d9b4134 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#6 0x00007f2e2d9aea43 in QObject::event () from /usr/lib/libQtCore.so.4
#7 0x00007f2e2c253c3d in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#8 0x00007f2e2c25b9ba in QApplication::notify () from /usr/lib/libQtGui.so.4
#9 0x00007f2e2e2f15db in KApplication::notify () from /usr/lib/libkdeui.so.5
#10 0x00007f2e2d99fd61 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#11 0x00007f2e2d9cbab6 in ?? () from /usr/lib/libQtCore.so.4
#12 0x00007f2e2d9c81fd in ?? () from /usr/lib/libQtCore.so.4
#13 0x0000003004639d3b in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#14 0x000000300463d50d in ?? () from /usr/lib/libglib-2.0.so.0
#15 0x000000300463d6cb in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#16 0x00007f2e2d9c815f in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#17 0x00007f2e2c2e5a6f in ?? () from /usr/lib/libQtGui.so.4
#18 0x00007f2e2d99e682 in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#19 0x00007f2e2d99e80d in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#20 0x00007f2e2d9a0cbd in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#21 0x00000000004908b8 in main (argc=1, argv=0x7fff379223f8) at /build/buildd/kdeedu-4.1.4/step/step/main.cc:58
Comment 1 Glen Kaukola 2009-12-17 11:27:15 UTC
What are you doing exactly when you "create a point"?
Comment 2 Alex Riesen 2009-12-17 11:50:57 UTC
It's been a *very* long while back, you know?

I vaguely remember selecting a point from the toolbar to the left,
moving the mouse pointer over to the graphics area and pressing left mouse button.

I may be wrong, of course. One shouldn't wonder, though. After all this time.
Comment 3 Florian Apolloner 2010-12-07 15:14:27 UTC
I can reproduce this bug. Create one particle, then add an anchor to it. Add one stick somewhere in the world and go to it's properties. Put "particle1" for body1 and you got it hanging…
Comment 4 Justin Zobel 2020-12-03 22:44:27 UTC
Thank you for the report, Alex.

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.
Comment 5 Alex Riesen 2020-12-04 06:21:00 UTC
Created attachment 133863 [details]
attachment-25814-0.html

No. I don't care anymore.

On Thu, Dec 3, 2020, 23:44 Justin Zobel <bugzilla_noreply@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=187686
>
> Justin Zobel <justin.zobel@gmail.com> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>          Resolution|---                         |WAITINGFORINFO
>                  CC|                            |justin.zobel@gmail.com
>              Status|CONFIRMED                   |NEEDSINFO
>
> --- Comment #4 from Justin Zobel <justin.zobel@gmail.com> ---
> Thank you for the report, Alex.
>
> 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.
>
> --
> You are receiving this mail because:
> You reported the bug.
Comment 6 Bug Janitor Service 2020-12-19 04:34:33 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 7 Christoph Feck 2020-12-28 23:50:08 UTC
Thanks for the update; changing status.