Possible memory leak/overconsumption of Dashboard using Chrome on Win7 and Win10

#1

I’ve been using the dashboard a lot today, duplicating/optimizing +/- 50 pistons to a new instance, stopping/deleting on old instance.

I had to restart Chrome on multiple occasions to flush memory as it was rapidly increasing in consumption, from about 150mb to 900mb. I had only two open tabs, my two instances of WebCore.

I can’t say for sure but it didn’t happen in the past so it might be related to the new design.

Speaking of the new design, it is truly awesome, thanks to anyone on worked on it.

#3

I wonder if my issue is related - I could not save a piston with more than 24 “chunks” last weekend. Tried on different computers. When saving the piston, the chunk count runs up to 24 but that is far as it got. It stops before the “Finishing Up” (Is that the message?) at which point it goes back into editing mode.
I tried cleaning the cash, but that did not help.

#4

Failing to saving pistons is often due to an incorrect expression within.

WebCoRE has to convert the expression to be understood by ST and a fault in syntax therefore causes an error.

#5

@jkp I gave it a try even if I didn’t see how one could be related to the other. It unfortunately didn’t clear my RAM.

@949BFN as Robin said, it’s not related.

@Robin I tried with a different computer (same browser tho) today and the result is the same, extensive usage lead to excissive memory usage. It’s not a big issue tho if I’m the only one to report and there is so many factors that can cause the issue.

#6

Clean and rebuild cache in the ST app doesn’t clean up your browser cache… just your pistons.

Hard refresh the browser instead (hold CTRL whilst clicking the browser refresh button with your mouse)

#7

Thank you, Robin, but that was definitely not the issue. I would have picked it up. And I tried many different possibilities. As soon as the piston gets to 24 chunks, it fails to save. (I’ve had this before by the way.)

#8

Can you see any errors in the IDE whilst saving?

#9

Did not think of doing that. Suppose it is because I did not realise that saving a piston will reflect in some or other way in the IDE log. Will check next time.