Bug 405453 - Massive memory usage in STEP
Summary: Massive memory usage in STEP
Status: RESOLVED WORKSFORME
Alias: None
Product: step
Classification: Applications
Component: general (show other bugs)
Version: 0.1.0
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Vladimir Kuznetsov
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-03-13 21:40 UTC by Franci_novi
Modified: 2022-10-21 05:02 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Franci_novi 2019-03-13 21:40:49 UTC
SUMMARY
When I modify the settings for the collision solver, the risk of a colossal memory usage is serious. More than 5 GB will be used if tolerance is set to 0.0000000001. That is not a problem when you have more than 5 GB of free space, but unfortunately this is not my case. I think it would be a good idea if a message of warning appeared before starting the simulation.

STEPS TO REPRODUCE
1. Create a circle of infinite mass
2. Create a particle that will collide with the circle.
3. Before starting the simulation, set the tollerances of the solver1 and the collision solver to very low value.
4. Start simulation.

OBSERVED RESULT
5 GB of internal memory is used (in my case this means a full memory occupation), and my computer become very slow even after the crash of step. The only way to go back to normality is reboot and free memory by command line.

EXPECTED RESULT
Before starting the simulation, a warning message should appear, like "You are going to waste 5 GB of your memory, are you sure? If not, change tolerance parameters."

SOFTWARE/OS VERSIONS
Linux 4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:33:07 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

ADDITIONAL INFORMATION
Comment 1 Justin Zobel 2022-09-21 03:14:00 UTC
Thank you for reporting this crash in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the crash with a recent software version?

If you can reproduce the issue, please change the status when you reply to "CONFIRMED" when replying. Thank you!
Comment 2 Bug Janitor Service 2022-10-06 04:51:00 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 3 Bug Janitor Service 2022-10-21 05:02:05 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now 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

Thank you for helping us make KDE software even better for everyone!