Tincta icon indicating copy to clipboard operation
Tincta copied to clipboard

Tincta occasionally freezes even with short files

Open Adina77 opened this issue 4 years ago • 6 comments

I was typing in Tincta (version 4.2), single open file, for about 40 minutes, about 95 lines of code. Plenty of memory. Not using any menus or special key combo, etc, just simply typing. Tincta became unresponsive and I had to force quit. I recall this happening before, so it happens occasionally. I am using an older system (Mac OS 10.11) so it may be related to that. Probably not relevant but the language selection was Haskell.

Adina77 avatar Oct 27 '21 06:10 Adina77

Thanks for reporting this. Does Tincta eat up a lot of memory in that situation? (Usually Tincta only takes around 50-100 MB) If there is a memory leak, it might be related to syntax coloring and in that case it might be linked to the selected language.

greimers avatar Nov 09 '21 19:11 greimers

Thanks for the response! I will look, the next time it happens. But I stopped using Tincta due to the issue (even though I liked it otherwise!). So, I will test it when I have some time. I was almost certainly using it with C++ (or perhaps Python), so it would be for sure a popular language. I will let you know if I discover any details that might help. Thanks!

Adina77 avatar Nov 09 '21 19:11 Adina77

This happened several times to me, mostly while I double clicked on the window title to make the window bigger. Then it eats 100% CPU, uses 3 GB RAM and become unresponsive, had to kill the process. I'm on M1, unsaved short normal text and no syntax highlighting was used, Tincta was open for ~45 minutes.

endo64 avatar Dec 18 '21 21:12 endo64

It is very interesting TextEdit also freezes with a very similar manner. I opened a text file, a few seconds later it freezed and it uses 9 GB RAM. Issue might not be related with Tincta, it might be an OS issue.

endo64 avatar Dec 28 '21 13:12 endo64

I think macOS Monterey had some memory issues in the initial release. Do you also have this issue on macOS 12.1? (I can't reproduce it on 12.1)

greimers avatar Dec 31 '21 12:12 greimers

@greimers I'm still on macOS 11.4 (M1).

endo64 avatar Jan 03 '22 06:01 endo64