Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Memoryleak in Pythonista 3 and 2.1
See original GitHub issueThere seems to be some sort of memory leak in StaSh.
When entering a command or an empty line in the StaSh commandline, the amount of objects in gc.garbage increases (write gci status to the StaSh prompt to get the amount of garbage).
When setting the debuglevel of the garbagecollector to DEBUG_LEAK, it will print a huge list of uncollectable objects, most of them appear to be some UI-Buttons on objc-level (write gci debug 62 to the StaSh-prompt to set debug to DEBUG_LEAK).
I have tested this with Pythonista3 (2.7.5), Pythonista 2.1 and 2.
Pythonista 2.0 does not seem to have any issues.
Pythonista3 and Pythonista 2.1 have memoryleaks when running StaSh.
Running normal scripts outside StaSh does not result in any memoryleaks.
The size of the garbage exeeds 1MB pretty fast.
I have tested this with the ywangd/dev branch.
Issue Analytics
- State:
- Created 7 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I am not working on new releases. Simply do not have any time for it at this stage …
@steljas sorry for the delayed response. It appears like this was a bug in the pythonista UI module related with keyboard inputs (the increase in garbage was proportional to the numbers of keys pressed since the last check) and was fixed a few weeks later in a pythonista update. Thanks for reminding me to close this issue.