Hot answers tagged memory-leak
Xcode has an app called Instruments and you can use it to gather all sorts of CPU and memory statistics both live as the device runs and to save for analysis over time. This use of the tool doesn't require a developer account, any paid software, or a jailbroken device. You do need to set up the devices in Xcode's organizer to indicate you wish to use them ...
This inconvenience is caused by a finder prefs entry: "show in new window: all my files" this is consuming too much mem. Select a different folder and all is fine
The core of OS X is not garbage collected; IOKit's libkern C++ Runtime requires developers to manage their own memory. Mac Memory Management From How does memory management work in Mac OS X? Apple documents the lowest levels of the Mach Kernel and the virtual memory subsystem fairly well on the web as part of it's developer documentation. ...
OS X (and all modern operating systems) is designed to use all of the memory that's available, for file caches if it has no better use for it. That's not a problem, since memory used for file caches is still available for applications to use.
I can't say much about preventing this, but there is no need to reboot. Just kill Finder, using Force Quit from the apple menu or killall Finder in a Terminal window. A new Finder will then be started in the old one's place.
Stability is hard to prognosticate - even if you have all the crash data that is sent to Apple or by harvesting the logs of thousands of Mac computers. Projecting the stability of a system in general to one person't specific list of modifications generally makes these comparisons poor and subjective. What I can say is that 10.10.5 is more secure than ...
While valgrind can be installed, the current state isn't very usable. In a simple program I got the following result; ==16016== ==16016== HEAP SUMMARY: ==16016== in use at exit: 63,264 bytes in 364 blocks ==16016== total heap usage: 516 allocs, 152 frees, 67,154 bytes allocated ==16016== ==16016== LEAK SUMMARY: ==16016== definitely lost: 8,624 ...
The Instruments app (part of Xcode) is a very good way to look for leaks and run stress tests on the memory allocation of a running program.
Here's my guess, assuming your Mac has an integrated GPU (eg Intel Iris Graphics). When you have your thesis open in Preview, graphics card memory is used to hold the image ("texture") of the Preview window, and perhaps also some off-screen-but-decoded pages from the thesis. With an integrated graphics card, the video memory is actually (partially?) ...
It looks like uninstalling Windows via bootcamp did not merge the space reclaimed by removing the old windows partition into your Macintosh HD one. In order to do that you can use the Disk Utility. You can simply drag your Macintosh HD partition bigger and apply it. Here is a tutorial on how to resize partitions with Disk Utility
To answer your question, yes, applications and processes continue to start up and if you have not manually closed them or restarted the computer, you will be "losing" RAM. You can turn the inactive memory into free memory with this command in Terminal: sudo purge You can also run Activity Monitor to diagnose what apps are running and sort the list by most ...
I would file a ticket with Apple. It needs to be addressed, and Apple is very good about following up. http://www.apple.com/feedback/macosx.html
Here's what I would do to actually try and fix the problem. We will completely reset iMessage. First up, log out of all accounts from Messages and Facetime, and then close them down. Create two folders on your Desktop: Messages, and Preferences. With Finder as the active application, hit shift ⌘ cmd G and enter in ~/Library/Messages/. Drag the contents of ...
Activity Monitor has columns that are not displayed unless you ask for them. Try "View -> Columns -> Real Memory". If you show All Processes, you may be able to find the process(es) that are tying up memory. You can click on a column to sort the results. My current machine has process 0, kernel_task, at 1.55 GB. Firefox has 1.04 GB. Surprised me. ...
I don’t really know the right answer, but I have a guess. You mention that you use safari on Windows, but you don’t mention the window’s version. In any case, the extreme load your computer had (in terms of RAM/HDD) might have caused a corruption in the Safari’s config and/or cache. Your computer, in an effort (desperate!) to save its information and write ...
Assuming you can be bothered, if you install MacPorts you will be able to install a functioning Valgrind (3.8.1 as for today) on your system. Unfortunately MacPorts will require you to install the whole XCode, not just the CL tools, so YMMV.
Only top voted, non community-wiki answers of a minimum length are eligible