Memory Usage on (47)
Completed
After updating to (47) memory usage just kept going higher and higher.
I quit and restarted nvUltra and the memory usage settled down.
macosxguru
-
The memory again spiked when I added the notes folder to nvUltra.
It is 14.3 meg folder with about 1250 files.
When this is not loaded, the memory usage is at
macosxguru
0 -
ok so don't update to 47 is what you're saying? :p i've only got 8GB of RAM...
0 -
:)
No. Update away. See the memory spike and enjoy the excitement of beta testing a favorite application.
This is how bugs get identified and squashed.
macosxguru
0 -
It looks like Apple's PDFKit leaks/retains/something memory like there's about to be a national shortage.
Disabling indexing the contents of PDF files drops the memory usage way down. It looks like others have noticed similar things with PDFKit on stackoverflow....
It doesn't appear that I am able to do anything to fix this, and it might have to wait until macOS/iOS gets fixed? That's not very satisfying....
That said, I did do a few things:
1. Fix a memory leak with indexing iThoughts files.
2. Fix some retained object cycle issues that wasted memory when opening and closing a folder
3. Fix an issue that unnecessarily re-indexed some files that had not changed, which could include some PDFs. This will at least prevent continuing to waste memory when a folder containing PDFs is reopened.
0 -
This folder contains a bunch of text files. Nothing else. So it might not be PDFKit responsible for my particular use case. Will see how the update deals with it.
macosxguru
0 -
Another issue -- there was a retain cycle like issue that prevented the preview views from being released when a window was closed. Unfortunately, fixing that leads to a crash on 10.14 (and possibly earlier.) To the best of my debugging skills and Google-fu, this seems to be a problem with macOS, though it must be a strange edge case to not be a more visible problem....
The next version:
1. Properly releases the preview views when closing a window when running on macOS 10.15+. This fixes a source of leaked memory.
2. Does **not** fix the issue on 10.14 and below, because that causes a crash.
3. Does a couple of other things to try and limit lost memory that was not being picked up by ARC (likely my fault, but the changes I made seem unnecessary).
0 -
(48) seems to have solved the memory issue on High Sierra and Catalina for me.
It is behaving well for me, Thanks.
macosxguru
0 -
Good to hear. As noted, there is now a known small memory leak in High Sierra (basically the preview never gets closed out when you close a window.) This should be a small amount of memory, but will mean that the app should be restarted periodically.
If you notice anything new, please open a new topic in the forums and we can dig further.
0
Please sign in to leave a comment.
Comments
8 comments