mjmarino
Level 1 (0 points)

Q: web browsers crashing and using up RAM on new Macbook Pro

Hey everyone,

 

Recently I bought a Mid 2014 Macbook Pro to replace my old 2011 model that was destroyed by liquid damage. Though I like this new computer, I seem to always have an issue with it running low on memory, ESPECIALLY when using web browsers such as Firefox and Safari. Quite often I will be waiting for a URL to load or will try to scroll through a webpage when the browser will freeze and crash. I've been keeping more of an eye on how much of my 8GBs RAM is being used at any current moment, and typically it is ranging from 2 GBs free to around only 30 MBs free as run applications such as Pages, Firefox, and/or Safari. These issues have been preventing me from using software such as Photoshop and Avid Media Composer because I keep wondering if the computer can even handle such memory intensive software if it cannot handle web browsers. Also when a browser crashes, I never seem to get a crash report and typically have to Force Quit the software.

 

It seems extremely odd that my computer is constantly running into these issues. My last model had less RAM, yet I never seemed to have an issue with memory or crashing. Part of me is wondering if I have an application somewhere that is consuming too much, or if I accidentally imported some broken files/applications from my previous computer, or whether it is either the web browser's software or the computer itself.

 

Below are my specs:

 

MacBook Pro (Retina, 13-inch, Mid 2014)

Yosemite 10.10.2 (14C109)

2.6 GHz Intel Core i5

Memory 8 GB 1600 MHz DDR3

Graphics Intel Iris 1536 MB

Media Name:    APPLE SSD SD0128F Media     Size:    120.47 GB (120,473,067,520 bytes)

 

 

Software i typically am running for work:

Safari Version 8.0.3 (10600.3.18)

Firefox 36.0.1

Pages 5.5.2

 

Any help would be very much appreciated!

MacBook Pro with Retina display, OS X Yosemite (10.10.2), null

Posted on Mar 11, 2015 4:42 PM

Close
mjmarino

Q: web browsers crashing and using up RAM on new Macbook Pro

  • All replies
  • Helpful answers

  • by OGELTHORPE,

    OGELTHORPE OGELTHORPE Mar 11, 2015 4:42 PM in response to mjmarino
    Level 9 (52,776 points)
    Mac OS X
    Mar 11, 2015 4:42 PM in response to mjmarino

    What you need to understand that the newer OSX's use RAM differently that what you are used to:

     

    https://support.apple.com/en-us/HT201464

     

    Foe efficiencies sake, the OSX will try to use as much RAM as is available.  The new metric is 'pressure' not amount.  To test, run your resource intensive applications and look at the results.

     

    Ciao.

  • by Linc Davis,

    Linc Davis Linc Davis Mar 11, 2015 6:28 PM in response to mjmarino
    Level 10 (208,037 points)
    Applications
    Mar 11, 2015 6:28 PM in response to mjmarino

    Launch the Console application in any of the following ways:

    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)

    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.

    ☞ Open LaunchPad and start typing the name.

    Step 1

    For this step, the title of the Console window should be All Messages. If it isn't, select

              SYSTEM LOG QUERIES ▹ All Messages

    from the log list on the left. If you don't see that list, select

              View ▹ Show Log List

    from the menu bar at the top of the screen.

    In the top right corner of the Console window, there's a search box labeled Filter. Initially the words "String Matching" are shown in that box. Enter the name of the crashed application or process. For example, if Safari crashed, you would enter "Safari" (without the quotes.)

    Each message in the log begins with the date and time when it was entered. Select the messages from the time of the last crash, if any. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.

    ☞ The log contains a vast amount of information, almost all of which is irrelevant to solving any particular problem. When posting a log extract, be selective. A few dozen lines are almost always more than enough.

    Please don't indiscriminately dump thousands of lines from the log into this discussion.

    Please don't post screenshots of log messages—post the text.

    ☞ Some private information, such as your name, may appear in the log. Anonymize before posting.

    Step 2

    In the Console window, select

              DIAGNOSTIC AND USAGE INFORMATION ▹ User Diagnostic Reports

    (not Diagnostic and Usage Messages) from the log list on the left. There is a disclosure triangle to the left of the list item. If the triangle is pointing to the right, click it so that it points down. You'll see a list of crash reports. The name of each report starts with the name of the process, and ends with ".crash". Select the most recent report related to the process in question. The contents of the report will appear on the right. Use copy and paste to post the entire contents—the text, not a screenshot.

    I know the report is long, maybe several hundred lines. Please post all of it anyway.

    If you don't see any reports listed, but you know there was a crash, you may have chosen Diagnostic and Usage Messages from the log list. Choose DIAGNOSTIC AND USAGE INFORMATION instead.

    In the interest of privacy, I suggest that, before posting, you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if it’s present (it may not be.)

    Please don’t post other kinds of diagnostic report—they're very long and rarely helpful.