Low memory issue

I have an HP Pavilion 2 Quad Proc 2.5 Ghz. Vista 32 bit home prem, 4 GB DDR2, 512 MB Nvidia 8500GT, Realtek Audio (updated driver), Blu ray read/write drive, Two 500 GB interinal drives 7200rpm SATA 3GB, Virtual mem set to windows control. Program PE7
I shoot video on a Canon SX1 IS. in 1920 x 1080 30f/s h264 MOV files. If I edit less than 4 Min of Video in PE7 all is well. 5 min of video causes low mem warning from PE7. No message from Windows. Adobe tech support said it is a windows virtual memory issue talk to Microsoft, but nothing else. I have HP support but they said it is outside the scope of support. For $ 60 I can get better support one time but no guarantee. I tried Reg cleaners, manual setting virtual mem at 18 GB. That helped a little. Rebooting helps., but in the end I get "program not responding" or other failure messages. I have read other posts but they were talking 40 min of video or more. I have had no problems with video from my old Sony I have edited over 1 1/2 hr. but 5 min of DH video brings it to a halt.Is anybody editing from this model Canon with sucess? I can play video from the camera with HDMI cable and it is beautiful. Any ideas?
Richard

Steve
I can understand how it would help process time but helping memory is a strange concept. Since less compression means bigger files. Memory management is way beyond my understanding. I have been working with computers since the PET and TRS80 with 2 kb upgrade and I want to use a hammer some days. I feel Adobe has a way to go with Memory management so that we can just open the program and edit video. I can understand taking a long time to process data in virtual memory but why the "program stopped" message? It is as if virtual memory is not used. Also data not used at the moment could be sent to the disk. It would be a lot slower but no memory crash. I can remember running large databases on 8 bit machines with 64 kb of memory. Of course a large database was smaller than one or two sec of video.
Thanks for the reply
Richard

Similar Messages

TS1702 How to fix low memory issues when restarting iPod doesn't work?

I am having trouble with several apps ceasing and my on screen keyboard having serious delays, it appears to be low memory.

Once you get to the sliding bottom row you touch and hold any app until they all start to wiggle. Then tap circled minus sign by all the app the "delete" them. Then click the home button to get back to normal. Then power off by depressing and holding the Power button until you get the slide to power off slider. Slide that slider. The turn on the iPod

Is this a low memory issue, or something worse?

I'm currently running Logic 9.1.6 on a new imac 27" with 16GB RAM. Just about all my libraries are running from a 4TB RAID system. It's not ideal for my purposes ( certainly compared to my "normal" studio setup), but I was delghted with just how much this computer can handle with that amount of memory onboard. However, there is a fly in the ointment, which I hope someone may explain.
Generally, I'm running a very large orchestral/"filmscore" template. Most of this is being hosted by Kontakt, with a few other bits and pieces thrown in: softsynths, Omnispher, Stylus,etc. But chiefly, it's all orchestral. When currently fully loaded, the Konatakt memory server is showing around 5.5 GB RAM used, which is pretty fantastic considering how much orchestral stuff is loaded up. I'm also working, on average, with around three instances of Altiverb, with groups of Kontakt instruments sent to whatever reverb is appropriate. The output has a simple, single Waves L2 on it. But, and here's the BIG but, despite the fact that I'm well within the RAM limit of my 16 GB. Logic, combined with the OS, is totalling around 13.5 BG of RAM which seems excessive,correct me if I'm incorrect on that. Worse, sometimes Logic starts to behave very oddly, particularly in terms of its GUI. Sometimes, if I choose to load up a couple more instruments, and then begin scrolling around the GUI seems to "collapse" in on itself and tracks start to "merge and dissolve", like the OS is having serious trouble in redrawing the graphics of Logic. Sometimes, also if I launch a Kontakt instance in this condition, the slots appear empty. In fact, I've evn had them actually unload entire 16 slots of instruments from Kontakt, I presume in an effort for Logic or the sytem to conserve RAM, which I find puzzling.
If left to continue, I usually end up with what I would describe as a damaged song. At that point even clicking on the mouse once send this brilliant white flash all over the screen, each time I click. Eventually, Logic will "collapse" and crash, and I know then that further attempts to relaunch this song will result in the same metling graphics and crashing, ultimately rendering the song unusable. In the past I've resorted to exporting all the data as a MIDI file and had to import to a fresh template, which has proved hit and miss.
I'm assuming this is a memory related issue, yet I see that even with a fully loaded song such as this, I still have around 3.5 GB RAM spare. More than enough of a cushion to avoid such weird issues as I describe. Or no?!
Can anyone throw some light on this, please? Is it a RAM/redraw/ graphics issue, due to pushing the memory limits, or something more sinister?
Thanks.

OK, I thought you might be interested to read these results. I switched to 64 and rebooted the computer. Now, with the exact same song, the memory used is appromately 9.5 GB, instead of 13.6 GB! an impressive difference.
I haven't yet used this in anger, so I don't know what will happen regarding third parties. I did note, however, that upon launching Logic for the first time in 64 bit, the AU validation concerned itself with 30 potential problem plugins, as opposed to the full extent of them, which is considerably more. No bad results came back from the scan, although this doesn't mena I'll not experience issues.
When you said the experience was not great for 32 bit plugins in 64 bit, what exactly did you mean? Crashes? Plugins simply not workng at all?
Tomorrow I'll get to work like this and see what happens. I have to say I'm encouraged.
Now if only I could switch to Lion and all my plugins were 64 bit..........

Low Memory.

After setting for Mail for Exchange, my Nokia E7 phone shows low memory.
I checked C Memory & there are only important files & that too of small sizes. All major Applications are installed in Mass Memory only.
Is “Low Memory” issue due to Mail for Exchange? If so, is it possible to transfer / change the data of Mail Exchange to Mass Memory instead of Phone Memory? How?
Appreciate all the help.

I had this problem in my Nokia E72, hope its relevant.
go to office>file manager>phone memory>logs>eng>ods
are there multiple files. click on options select all and delete. if the no of files is quite large it will take a very long time to delete. or you can select 30-40 files and delete and then check the space. if the free space increases then you need to delete all.
also try updating your firmware.
Also checkout this thread http://discussions.nokia.com/t5/Eseries-and-Communicators/c-memory-low-on-Nokia-E7-00/m-p/1588222#M1...

Low memory/update = warranty phone replacement

Has anyone gotten a phone replacemnt under warranty with all the low memory and upgrade problems?

Why is the vendor response always a non-effective quick fix ? I have had my DINC since April 2010, and with Android 2.1, NEVER had a low memory issue.When Verizon updated the DINC to 2.2, I STILL, NEVER had any low memory issues. All of a sudden when I installed the 2.3.4 Gingerbread OTA update, I, like many others have had nothing but problems with Low Memory. I have cleared Facebook Data, GMAIL Data, and the problem sometimes clears, and sometimes doesen't. Even when it does, within an hour or 2, the low memory again pops up on my notification bar. All my mail settings are set to download the least amount of data possible. I've even tried uninstalling GMAIL, FACEBOOK, etc., and again nothing.
As I understand, there are 3 memory areas on the phone, and more than likely this problem relatest o the "Phone Memory" area which I believe is similar to RAM on a PC.
I have the error right now, and here is my storage information:
SD Card - Total Space 29.81GB
SD Card - Available Space 28.52GB, or 95.67% Available Space
Internal (Phone) Storage - Total Space 6.60GB
Internal (Phone) Storage - Available Space 6.28GB, or 99.68 Available Space
Phone Memory (RAM?) - Total Space 748MB
Phone Memory (RAM?) - Available Space - 407MB, or 54.4% Available Space
Please, can Verizon really look into this and find a permanent solution ?

Powerbook Lower Memory Slot Issue, what are my options?

Hi there,
I have a Powerbook G4 1.5ghz that I purchased in October of 2004. I had no problems with it until after upgrading the RAM to 2 x 512mb chips and then installing Tiger which resulted in me later notcing the missing RAM and learning about the lower memory slot failure issue.
I find that sometimes if I remove the RAM and try and power it up and then replace the RAM again that the lower slot ocassionaly does come back. Trouble is though that the machine will either crash or I loose the other RAM slot when I have to shut it down. It seems to be so intermittent this way and I'm tired of constantly removing the RAM to fiddle about with it.
My serial number begins W8441, so it isn't covered by the returns programe. I would call Apple Support, but I am put off by a £35 charge just to have them discuss and diagnose the problem.
I'm in the UK and as I don't have Applecare and I'm not elgiable for the returns programe can anyone tell me what they charge for a logic board replacment? Looking at what they charge in the US, it's not cheap.
I use my Powebook for Final Cut Pro, DVD Studio Pro, After Effects mainly and I had been alright with 1gig when it was working.
I'm really trying to decide what the best thing to do is....
- Do I pay for the logic board replacement, which I'm not really sure I can afford right now, or to be without my machine... especially as I have read that it can just fail again.
- Should I just buy a 1gig stick for the upper slot and try and sell my old RAM, as that would be cheaper than getting the logic board replaced?
It's a real shame that Apple doesn't seem to want to ackowledge that this effects other users as I'd been so impressed with everything about Apple up until now.
Thanks for any advice.

(Browse down for findings and questions).
The notorious lower-memory-slot-bug has hit my finally too... I never believed it until now (and I've immediately signed the petition).
I am outside warranty and I never bought Applecare either.
Also my powerbook, a very dear machine to me, is a less common type to have this problem: a 1 GHz G4 15" FireWire 800 OS 10.3.9 type. Funny enough my older powerbook ( a G3 Bronze) is still running strong with no problems whatsoever.
My G4 15" also has the "white spots" problem and a dead superdrive... I cannot believe how many hardware problems I'm having with this machine in comparison to all my older macs - even my sluggish powerMac 7200/90 never gave me this many headaches...
Alright, I'll stop complaining for now.
I've been able to browse the internet on this and found the following statements:
The lower memory slot gets "fried" because of a OS 10.3.9 upgrade,
or possibly due to overheating when the powerbook is put on the users' lap,
or possibly due to picking the powerbook up by the corners so the metal gets bent.
+ I have only seen one case where someone's UPPER memory slot was defective.
The solution to this problem (replacing the logic board) didn't seem to be definate in many cases so I'm reluctant to try this myself (and I have very little money). The alternative (replacing the upper slot memory with a bigger type of RAM) seems a bit scary to me,
because I wonder:
-will the upper memory slot RAM get "fried" eventually as well after a while?
-do you need to have something installed in the lower slot or is it possible to just install one RAM card only?
-are there more people with a 1 GHz PB that have this problem? It seems it's mostly people with a 1,67 GHz that have been bitten by this bug and maybe that's why Apple decided to give the majority a free repair. I am not sure whether that is a common policy, I am part of the minority it seems.
As a solutions someone posted on a board that we should all buy KTA-PBG4333/1G RAM, but here in Dutch stores it is said this memory is only compatible with 17" powerbooks....
Does anyone know if it is suitable for 15" as well??
G4 Powerbook Mac OS X (10.3.9) 1 GHz G4 Powerbook FW800

Low Memory Environment Render Issues...

Howdy folks,
     I've been working on a 13 minute promotional video for a non-profit summer camp. It is made up of mostly still images with some ken burns effects, a narration track, a music track, some titles, and some logo overlays.
     I am doing this on a 3.2 Ghz P4 with only 1.5G ram under XP sp3. I realize this is not an ideal PPro box.
     Windows XP is configured to use 2 drives for VM paging (3Gigs each). All drives have over 100gigs of free space on them.
     Now until recently I've only had a couple of small issues which I suspected were related to trying to do this in a low memory environment. In one case a flash render would die at the same point every time (error was something along the lines of "did not return a valid frame"), and simply scaling down the still image clip at that point in the sequence so that it was closer to the project size took care of it. That method also helped in a few cases where some images would not render at all, and just appeared as black screens in the final video (the render process did not fail, but the end result was missing clips).
     Then there was one case it seemed to fail at random points. A simple reboot took care of that, and it exported just fine.
     But now, however..... Now it's back to failing at random points (sometimes it gets 3500 frames in... sometimes as far as 13400... or anywhere in between) and additionally, by viewing the incomplete flash video file with VLC (which I need to do in order to find out where it failed because PPro never tells me) I find that some of the images are black screens, as before.
     The problem now, is that it's never the same point of failure, and it's never the same images blacked out. And rebooting and or killing off extra processes does not help.
     Now this was rendering fine last week. Here's the kicker - I haven't changed much of anything since then. The project is still the same length, with just about the same number of cuts, tracks, and assets used. The only things I've done since then are:
     1) I duplicated the sequence so that I can make some changes unique to the web-version of the video, and still save the old sequence to go back to. The old sequence has remained untouched and I haven't even looked at it since then.
     2) Created 2 new titles and inserted them in place of some old ones in the new sequence which weren't appropriate for the web version of the video (only the text is different in these new titles... they are the same style, size, etc. as the old ones they replaced)
     3) I shortened some empty time/space/pauses between sections of the sequence.
     So those are all minor changes... but I can't shake the rendering issue no matter how many times I restart or scale down an image that was blacked out or appears at one of the random points of outright failure (again, with the "did not return a valid frame" issue).
     I did notice that after I duplicated the original sequence, the project takes much longer to open. Does having another sequence present in the asset bin use that much more resources? Even if the clips in that 2nd sequence use the same assets as another? I'm tempted to remove the original sequence and see what happens, but I don't want to lose it and have to un-edit the web version whenever I want to go back and re-render the DVD version.
     So basically I'm looking for anything that might cause the small changes I made to be giving me so much grief now.
     Any input is appreciated. Thanks.

You may have a corrupt project. Try creating a new project and importing the old one into it.
If you still experience problems then carefully do each of these troubleshooting tips. One or more of them is likely to help.
Cheers
Eddie

Having issues with low memory that is causing some of my apps to crash, need help please !!!

Having issues with low memory that is causing some of my apps to crash, need help please !!!

Is the device actually showing low memory errors?
What is really occurring?
Basic troubleshooting from the User's Guide is reset, restart, restore (first from backup then as new). Has any of this been tried?

Rendering and Low System Memory issues in PE9.

Hello again.
N.B: I am an ex-PE3 user.
I am having a few issues with PE9.
1. My main issue is that I am regularly getting the 'low system memory; please proceed with caution' message. I have googled it and read people's suggestions, but am not sure where to go from here. I have tried saving my file under another name, but am already up to '....E' (fifth) version of the file I've been working on this afternoon. The total time of the project is only approx 45 min's, although I will say that this 'low system memory' issue seems to be worst today, as I'm adding more still photos.
2. One of the suggestions made by Steve G on one of the forums was to make sure projects are regularly rendered. When I hit 'Enter' to render, the little render window pops up for a split second and then disappears. And I would assume from the red line above my timeline that my file is not rendered.
3. When I switch to 'Sceneline' view, my horizontal scroll-bar across the bottom will only drag SO far (to a certain point in my project; but definitely not to the end of my project. It is really frustrating. I sometimes can fix it by flicking between Sceneline and Timeline, but I have to do this multiple times... and it seems a ridiculous way to do it.
It would be fantastic if someone could help me with these issues, please!
System details:
AMD processor 3.2 Ghz
4 gig RAM (3.12 gig usable)
Windows 7 Ultimate

Hi everyone:
Thankyou for all your suggestions.
Sorry, Bill, but both those links give me an error message. I was all set to read them, but they won’t work, unfortunately.
What is meant by ‘page file managed’, sorry? And do you mean ‘hard disk drives’ by HDD, or does it stand for something else in this context? I’m not sure what you mean by how do I have them allocated. Again, apologies for my ignorance. I do have only one HDD, but it is partitioned.
The image sizes all seem to have a depth of 24, but vary in dimensions – I can see that some are quite large (around 3 mg in size, with dimensions of 4288x2848, for example). Is the actual mg-size relevant, or only the physical length and width?
I have tried to look at the frame size of my project, but it seems to be greyed out. In pale digits, there is 720x576 written.
Just before I sent this, I thought of one other thing to try first.
I tried starting a ‘New Project’. I then inserted just 6 still photos, for experimentation purposes. I then hit ‘Enter’ and the Rendering window came up and appears to have rendered correctly. So I then tried looking at one of my other projects (that hadn’t previously been rendered) and tried to render it. In this case, as in for the project I am currently working hard on, the Rendering window flashes up for about ¼ of a second and then disappears.
What is going on???
From: Bill Hunt [email protected]
Sent: Friday, 11 March 2011 2:00 AM
To: rachel jewiss
Subject: Rendering and Low System Memory issues in PE9.
although I will say that this 'low system memory' issue seems to be worst today, as I'm adding more still photos.
What are the pixel x pixel dimensions of those still images?
What is the Frame Size of your Project?
How is your Page File Managed, and what is the size? This http://forums.adobe.com/thread/632449?tstart=30 will give you some background and tips.
Also, tell us about your HDD's, and how you have them allocated.
For more discussion on Rendering, please see this http://forums.adobe.com/thread/794719?tstart=0.
Good luck,
Hunt

Low system memory issue - caused by Mail?

While I was at work, my wife was using our iMac at home, and she said that a weird error dialog appeared this afternoon that asked her to quit applications, following which the system became unresponsive.
When I came home I found that a lot of running applications were in a hung state (unresponsive and required a Force Quit) so I rebooted the iMac.
I looked in the Console and saw that at 15:39:37 today two errors started repeating at an enormous rate - something like 5000 times per second for the next 5 seconds:
12/02/2015 15:39:36.373 Mail[226]: *** Assertion failure in -[MCSocket readBytes:maxLength:error:], /SourceCache/Mail/Mail-2070.6/MailCore/Networking/MCSocket.m:469
12/02/2015 15:39:36.381 Mail[226]: exception parsing IMAP response: trying to read/write concurrently
...then at 15:39:42 the rate suddenly decreases to only about 10 errors per second. This continued for a further 15 minutes, until at 15:55:22:
12/02/2015 15:55:22.000 kernel[0]: low swap: suspending pid 226 (Mail)
12/02/2015 15:55:22.590 loginwindow[797]: -[ProcessPanel(lowMem) initAsLoMemPanel] | Lo-Memory panel initializing
...then lots of errors like this:
12/02/2015 15:55:23.000 kernel[0]: memorystatus_thread: idle exiting pid 999 [com.apple.MailSe]
12/02/2015 15:55:24.000 kernel[0]: memorystatus_thread: idle exiting pid 1000 [com.apple.InputM]
12/02/2015 15:55:25.000 kernel[0]: memorystatus_thread: idle exiting pid 269 [com.apple.intern]
So it looks to me like the Mail app went haywire, the Mac ran low on memory, so OS X made some kind of "Lo-Memory panel" appear to handle it.
A quick search in Google Images revealed that there is such a thing as an OS X low memory error - the exact text of which is "Your system has run out of application memory. To avoid problems with your computer, quit any applications you are not using". It displays a list of running apps so you can quit them. The error looks something like this:
    http://i.imgur.com/HDplIwv.jpg
When I showed this picture to my wife she said that is exactly what she saw.
I will report this to Apple on their feedback page. If anyone has any other suggestions let me know. Obviously something that can bring down the entire system like this is not good.

There is excessive swapping of data between physical memory (that is, the memory chips on the logic board) and virtual memory (one or more files on the startup volume.) That activity is relatively slow and causes the whole system to be less responsive. It can happen for two reasons:
          A long-running process with a memory leak (a kind of bug)
          Not enough memory for your usage pattern
Please note that if the cause is a memory leak, installing more memory will not help. That's likely if you already have more than 4 GB of memory. Tracking down a memory leak can be difficult, and it may come down to a process of elimination.
These instructions are for OS X 10.9 and later. Some details may be slightly different for earlier versions of OS X.
When you notice the swap activity, open the Activity Monitor application and select All Processes from the View menu, if it's not already selected. Select the Memory tab. Click the heading of the Real Mem column in the process table twice to sort the table with the highest value at the top. If you don't see that column, select
          View ▹ Columns ▹ Real Memory
from the menu bar.
If one process (excluding "kernel_task") is using much more memory than all the others, that could be an indication of a leak. A better indication would be a process that continually grabs more and more real memory over time without ever releasing it. Here is an example of how it's done.
The processes named "Safari Web Content" render web pages for Safari. They use a lot of memory and may leak if certain Safari extensions or third-party web plugins are installed. Consider them prime suspects.
Another process often implicated in memory leaks is "inkjet4" or "inkjet8," which is a component of the HP printing software. If it's present, force-quit the process in Activity Monitor to solve the problem temporarily. Empty the print queues in the Printers & Scanners preference pane (which has a slightly different name in each recent version of OS X.) If you don't use an HP printer, reset the printing system. Otherwise, if the problem is recurrent, update the software (which may not help) or contact HP support.
"Wired" memory should be a small part of the total. That memory is not swapped, but it makes less physical memory available which may then result in swapping. If you have a lot of wired memory, that's usually an indication of a memory leak in a third-party program that modifies the operating system at a low level. Ask for guidance in that case.
If you don't have an obvious memory leak, your options are to install more memory (if possible) or to run fewer programs simultaneously.
The next suggestion is only for users familiar with the shell. For a more precise, but potentially misleading, test, run the following command:
sudo leaks -nocontext -nostacks process | grep total
where process is the name of a process you suspect of leaking memory. Almost every process will leak some memory; the question is how much, and especially how much the leak increases with time. I can’t be more specific. See the leaks(1) man page and the Apple developer documentation for details.

Memory issues

I have a 2008 Macpro...remarkable up-to -date for its age...I plan to use it for some time yet. Lately I have been a having what seems to be a memory issue. There are 12 gig of Ram installed...6x2 gig each in pairs. Sometimes on boot the screen only shows a flashing folder. I shut down and reboot, and it seems fine...but only 8gig of ram shows installed. I opened it up, unseated the boards that hod the ram, and unseated and reset all he ram, and replaced the boards. Great, all he ram shows, 12 gig again. This morning, a few days later, it did it again, showing 8. So, when I run Crucial's memory analyzer, it shows first four slots full, last four empty. A few questions...are the first four slots the top board, the last four the bottom board? This, BTW, is what it was also showing before I reseated the ram. If so, the ram in question s on a separate board. Opinions, is the ram bad, or the board, or neither? Should I reseat again and flush with contact/tuner cleaner/degreaser? Could this hurt? (it is made to clean electronics) the machine does seem ever so slightly unstable. FCP crashed once in a 5 hour edit, which it has done before but rarely. The machine itself did not crash, just the program. Can using the machine like this do more damage, or will it just not boot? I feel it is a seating or connection issue, as I have never seen ram come and go, once it is fried it's fried. The ram is still pretty pricy, but I was going to buy 4 more gigs just to fill it out. Are the two board that hold the ram identical, top and bottom? If so, is a good diagnostic tool to swap them and see what happens? Move all the ram and swap board positions, or do I risk blowing ram ? Remember, the ram did show up when I reseated, so it seems like it is I damaged. My goal would be to see if top ram stops appearing. Does ram need to be filled in order? I know in pairs, but can I just swap the boards and leave the ram, which should look like filling slots 1,2,5,6,7,8...as opposed to 1,2,3,4,5,6. Can the boards be swapped, or are they set somehow to be 1-4 and 5-8, or is that determined automatically by their upper or lower insertion? Any other advice is appreciated. Funds are low, so I need to keep this machine running. Other info, 3.06ghz (2 quad core) Xeon CPUs, 1tb system drive, 4 TB raid5' OSX 10.6.8 dual graphics display with 512MB (can't remember card model right now). Also, can I update graphic card in this machine? I looked at it a few years ago, but the I for I found was confusing and I never got to it. I figure I might be able to get a better card pretty cheap by now. Thanks all.

You have typed a huge list of ideas all as one paragraph with many questions in it without a single bit of white space. My eyes are not good enough to read a question, attempt to answer it, then dig through the sea of letters to find the next question.
Your writing needs white space, which gives it a peculiar overall shape, and allows a reader with poor eyesight to return to a particular spot in the text. So I will attempt to answer some parts of your query, but will be forced to do so from memory of what you wrote.
The Mac Pro uses Error Correcting Code (ECC) RAM. Eight extra bits are stored with each word, and checked when read back. Single-bit errors are detected, and the check bits are used to make a correction on the fly. More complicated errors are detected, and can cause your Mac to halt on a kernel panic to prevent bad data from propagating.
ECC RAM means your Mac can detect bad memory easily at Startup, and can declare pairs of DIMMs "absent" to avoid using them.
Contact corrosion, which was an issue with much older DIMMs, is rarely an issue with these FBDIMMs. Once re-Inserted ONCE, corrosion will not recur for a year or more.
The upper and lower Riser-cards are identical.
The FBDIMMs in these machines are subject to overheating and death. If Mac OS X or any program reports DIMMs as missing, at least one of the DIMMs in that pair has died (but since they are installed in pairs, both are marked absent).

I want to ask something about firefox. why firefox use very much memory? can you develop to reduce memory comsume? this problem is very distrub in my PC with low memory.

I want to ask something about firefox.
why firefox use very much memory?
can you develop to reduce memory comsume?
this problem is very distrub in my PC with low memory.
== This happened ==
Every time Firefox opened

How much memory is Firefox using right now?
# Press '''CTRL+SHIFT+ESC''' to load the Task Manager window
# Click the Processes tab at the top. (Click once near the top of the window if you don't see tab
# Find firefox.exe, and see how many kilobytes of memory it's using.
Showing around 80MB when Firefox first starts is normal. Right now, I have 75 tabs open and it's using 500MB - this varies a lot depending on what you have in the tabs.
Other than high memory usage, what other problems are you experiencing? (Examples include slowness, high CPU usage, and failure to load certain sites)
Many of these issues, including high memory usage, can be caused by misbehaving add-ons. To see if this is the case, try the steps at [[Troubleshooting extensions and themes]]. Outdated plugins are another cause of this issue - you can check for this at http://www.mozilla.com/plugincheck

Firefox 3.6.8 and memory issues

After the last update to 3.6.6, I disabled plugin-container per the instructions given on the forum, and my RAM problems went away. However, after the automatic update to 3.6.8, the memory problems came back, with memory usage going up to 92%. I downgraded to 3.6.4, and turned plugin-container off again; while memory usage is currently at 84%, it is not as low as it was before the upgrade to 3.6.8. (79-80%) (There is very little difference in the websites being opened on the various tabs.)
== This happened ==
Every time Firefox opened
== I upgraded to 3.6.8

ffs guys. It's a free browser. It's cool. We love it. But can we do something about memory issues? Almost every release has huge memory leaks.
How about halving the release points and focus on memory issues for the other half of the time. I am a long time user since way back in the day and it seems to me that instead of trying to release so many versions, we should be focused more fixing the current release.
I say put a moratorium on new features until bloat can be fixed. These experiences are starting to give me a hardon for IE again.
Screw new features. I can deal with plain old tabs like they are. I don't need more bells and whistles. This browser has been kicking ass and taking names for a loonnnggggg time. We don't need more bloat. Keep the security fixes coming but everything else can wait. Take a breath. Stop and smell the roses for a few weeks.

Low memory on iPad 2

The diagnostics of my iPad 2 says that my iPad has low memory.however I have 21.5 GB available. Please help. Thanks

I had this same issue with the new ipad, I kept getting logs generated that stated low memory. I am not aware of any problems or issues this created, it was just sort of an informational warning not that there was anything wrong. To “fix” it I just closed all the apps still in memory by double clicking the home button, holding your finger on one of the apps in the bottom window until they shake then hit the x to close them out of memory.

"low memory" in exporting to progressive JPEG

hi, anyone knows how to deal with "low memory" or "low virtual memory" error when export file to progressive JPEG? it happens when file is from a few mb to 30 mb. if file is only under 1mb will be ok. I got pretty new pc: xp pro with dualcore 2.6 ghz and 4 gb ram, but it can not export 10 mb indd file to progressive JPEG. i did adjust page file to max 20000mb. but does not work. thanks for help.

it's only working a few times after computer got fresh start or restart, then"low memory" msg up again and can not to export progressive jpeg as 300 resolution. anyone has ever experienced this issue? is it possible that RAM type does not match with motherboard?

Low memory issue

Similar Messages

Maybe you are looking for