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
Solid Tools creates Memory Leak when used in loop #107
Comments
A "memory hole" has nothing to do with software ... As said in the public forum, it is called a memory leak ... |
Noted/updated Thanks
…On Tue, Jul 31, 2018 at 9:16 AM DanRathbun ***@***.***> wrote:
A "memory hole" has nothing to do with software ...
https://en.wikipedia.org/wiki/Memory_hole
As said in the public forum, it is called a memory leak ...
https://en.wikipedia.org/wiki/Memory_leak
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#107 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AO2aAvCAVzpMzlYUxbKt235B3DLz8vThks5uMFiWgaJpZM4VoOFQ>
.
|
Title describe a memory leak, but the description seems to indicate unexpected result in how the geometry appear after boolean operation. If this issue is related to unexpected boolean union, can you attach screenshots that indicate what you see and what you expect? If it's a report on memory leak, can you describe how you detect and measure the memory leak? |
Sorry, I will update behavior above. |
Just to clarify; the issue is the hang/freeze after the solid operation, and the occasional crash? Memory consumption here doesn't appear to be the main issue. (Also, a memory leak is allocated memory not freed. Just because memory usage increase doesn't mean there is a leak. When you do a lot of geometry changes it will add to the undo stack - which is kept in memory.)
So her union version never show the issues you describe? (I'll have to ask her for insight on what she is doing.) |
Hello Thom, correct... the issue is AFTER things seem to have completed. I suggested memory issues based on input from Dan Rathbun in this post: https://forums.sketchup.com/t/what-is-causing-this-script-to-hang/71421/3 I have no idea and certainly don't understand enough about how resources are allocated to do anything other than pass on Dan's wisdom! Correct... Enroth's routine worked perfect. No hanging. Thanks! |
The post is actually here: I also wondered in that post about SketchUp's autosave feature, and asked whether the model file was local or network (DropBox, etc.) Reviewing the topic thread, I do not see an answer to these questions.
I think it is a symptom of the problem. There is something happening that is taking time, blocking SketchUp and using memory. Ruby's garbage collection could also be kicking in after so many changes but shouldn't be taking 40 seconds. We'd also think that a save operation would complete in a few seconds if the save is to a local file. It is weird that he tried it on the same machine, under SU2015 and did not have the issue.
In the following post Hank explains what the begin and end memory states were, ... but does memory ever return to the before levels ? |
MacBook Pro (Retina, 15-inch, Early 2013)
NVIDIA GeForce GT 650M 1024 MB
Intel HD Graphics 4000 1536 MB
2.4 GHz Intel Core i7
8 GB 1600 MHz DDR3
(however also re-producable on other Mac setups)
Describe briefly what you are doing and what is happening.
Wanted to take a group containing many solid sub groups and union ALL of them by looping through each of the group's entities.
Describe what the expected result is.
The expected result would be a single group that has been unioned.
What happens: the operation will appear to complete, printing the appropriate time elapsed to the console, but then SU will lock up, with the spinning rainbow cursor. During this time, observing the memory usage in the Activity Monitor in this “afterward” period, Sketchup starts with at about 120 MB allocated and continues to jump upward by about 25MB increments until it peaks at 440 MB when SU finally begins to react again. The operation will be successful but will have hung for a long period. Sometimes SU will crash outright if too much geometry is fed into solid_ops_all_entities. Running the same operation with Enroth Union (commented out below) is almost instantaneous.
I have 8 gig of RAM, 3.4 of which is allocated when I start this operation and 4.5 when complete.
Attach any relevant files.
solid_tools_memory_leak.skp.zip
The text was updated successfully, but these errors were encountered: