Switch memory issue

I have cisco 2960G switch. I got below error message on switch at some interval.
"Memory on switch has insufficient capacity or is malfunctioning."
Switch model no: WS-C2960G-24TC-L
SW version: 15.0(2)SE2
SW image : C2960-LANBASEK9-M

Use 15.0(2)SE4.

Similar Messages

Memory issues AP3 & 10.9.1

I've been using Aperture since version 1.0 and never have I had memory issues until now.
HAs anyone come across issues with AP3 and 10.9.1
"Your system has run out of application memory" ? and shows Aperture in red (paused)?
I have 32GB ram, all SSD's and the ATI 5870 graphics card.
Any thoughts/insight/solutions?
I think I'm on the verge of just dumping Aperture and callling it a day - it's bad enough 10.9.1 is having issues with the finder.

This is a known issue.
It doesn't affect everyone, and for some people is resolved by switching off on-screen proofing.
The work around for the moment is periodic restarts before the system runs out of memory. Hopefully a fix will be along shortly.
Andy

Is Adobe planning on fixing memory issues or are they hoping Fireworks will go away?

When trying to use Fireworks for larger sites, we (and a lot of other people we talk to) have always had issues with Fireworks crashing (Mac and PC).
We try to split files when working on larger sites but if you use a lot of symbols, updating them is really slow - often slower than saving files and it doesn't stop the crashing.
I realise people might say we're asking for trouble designing pages that are 3000px - 4000px long but long scrolling pages often work well (http://www.apple.com/macbookpro/design.html http://www.kaleidoscopeapp.com/) and we find ourselves designing more and more of them.
When using Fireworks every day, you have to wonder if Adobe would prefer everyone switch to Photoshop - does anyone know what their plans are for Fireworks?
Practical suggestions for stopping the crashes would also be great!
Cheers
Ben

Thanks Jim,
We saw a dot release for Fireworks with the CS5.5 Suite
When I looked at CS5.5 I didn't see Fireworks - totally missed that!
Can you tell me, are you designing multi-page files at these dimensions? If not - good. If so, I would question why, considering that you need to move to Dreamweaver or another web editor to create the actual final site.
Wherever possible, we actually wireframe then design directly in HTML/CSS but on bigger sites, we use developers who like Fireworks files. Plus on the bigger sites, corporate clients often prefer seeing how key pages will look/flow with content in them before they go out for coding.
In these situations, we've tried both multi-page documents and single page documents. But with a lot of symbols, it's actually quicker to reduce the undos to 1, use multi-page docs and gingerly save after every change! We've found updating lots of symbols across multiple docs painfully slow.
Again, I am making a lot of assumptions here, so please forgive that.
No worries!
Also keep in mind that the MAXIMUM page dimension for a new Fireworks document is 6000 pixels. And it sounds like you're getting awfully close to it. FW does not have the same kiknd of memory management features that Photoshop has.
I guess this is the crux of the issue. We can load up the file size in Photoshop but Fireworks has so many features targeted to web design that it's hard to use Photoshop for this purpose.
I thought I'd read somewhere that Fireworks will only ever use 2GB of ram and I've noticed a similar thing in Activity Monitor - Fireworks seems to only ever take about 1.98GB of ram. However this is pure speculation and I don't know this for sure.
Anyway, thanks for the replies. I guess I was curious to see if anyone had heard what Adobe might be planning as the memory issue is surely well known to them - and it's obviously a conscious decision to not allow Fireworks to access more.
Unless CS5.5 addresses this?
Cheers
Ben

Premiere Pro CS3-CONSTANT Memory issues when editing/rendering/exporting

Alright, as said in the title I am currently using Adobe Premiere Pro CS3, and my issues are horrendous
No matter what, within 10 minutes of editing, Premiere will warn and then crash because of memory issues, starting with the message:
"Adobe Premiere Pro is running very low on system memory; please save your project and proceed with caution"
Also, whenever I try to export this project, within 800 frames of a 7000 frame project (currently), it displays the message:
"Error Compiling Movie", and then the previous message above if that hasn't already happened before
And eventually, the program will crash out of nowhere, with random windows errors
Here's my specs:
Intel i7 920 Processor
6 GB DDR3 RAM
Nvidia 480 GTX
750 watt power supply
24" Dell Ultrasharp Monitor
Now, I've noticed that whenever Premiere is getting close to crashing, my RAM gets up to around 4.7 GB being used, and then it crashes.
I have already gone into Edit-Preferences and tried switching from Performance to Memory; that hasn't fixed anything
I noticed that when I was just running my video over and over again, it stayed stable at 4 GB or so, so maybe its a rendering issue?
I have already tried lowering my number of processes running at any given time, including my antivirus program (Kaspersky) and even explorer, but it still crashes no matter what.
========================================================================================== ========
This is a SERIOUS issue for me, as even with all the normal crashes I could finish the video; but now I cannot even export my video at ALL without it crashing, and I have a plenty strong-enough computer to handle this, so what gives?
Please help

Ok, well this has been getting me nowhere
I tried importing (both my CTRL-X method, and literally importing the project), and now the program won't even RENDER the footage, it just errors out at 800 frames (just like exporting)
What is going on???
I used to use Premiere Pro 2.0 all the time, on a separate computer, but I have 6 GB of RAM, is this really impossible???
EDIT:
And now, even after finally getting it to render (by saving after rendering before what crashed, and then starting it up and rendering again), all my footage looks like crap XP

LR2 Memory Issues

LR2 seems to have memory issues. My most frequent experiences with these are:
- Exporting about 60-100 images at a time. Sometimes LR2 will export all of them, sometimes it will fail and tell me that it is out of memory. Exiting and restarting LR2 allows the export to complete. (I *do* like that it remembers which images were selected prior to exiting, it saves having to figure out what I had just tried to export. Kudos!)
- Sometimes when I export I get corrupted jpegs. Usually this is just before (or during) one of the above mentioned out of memory errors. I have to be sure to check everything that was exported to make sure it exported cleanly (major pain in the kazoo).
- Sometimes LR2 hangs and I have to use Task Manager to shut it down.
- Sometimes LR2 simply "gives up the ghost" and goes away on its own.
While I don't have proof of the last two being memory issues, I highly suspect that they are.
All of the above are on a Windows XP Home machine with 4G of memory.

Michael Shaffer -- the 1.5 to 2x RAM recommendation by Adobe engineers was specifically the Windows VM settings and has nothing to do with the scratch disk space (temporary files). Photoshop uses Windows' virtual memory management and page file, but it supplements that with its own management of the memory space allocated by the OS, rather than continually giving back memory when it's not immediately in use for image data.
Kenneth Daves -- I'm not sure what the URLs you cited are supposed to tell me. The first one confirms that the page file is used for disk storage of virtual memory and that memory is continually swapped or paged between RAM and disk; it also confirms that the maximum per-process memory space for Win32 programs is 2GB (unless they are compiled to use large addresses and the /3GB switch is used). The remaining ones discuss how memory usage differs in 64 bit OSs.
I agree that virtual address space is the better choice of words to describe the overall memory space used in Windows. Virtual Memory is typically used to refer more specifically to the page file. And now that I understand that your reference to 2 GB of User Space and Kernel Space was intended to describe the the default
maximum of each of those spaces (absent the /3GB switch and large address space compilation), I agree completely.
Yes, when an application has used all of its permissible virtual address space, needs a memory allocation, and cannot release any of the existing memory, it is "out of memory." However, Adobe complicates this somewhat, because when there is insufficient space for its scratch files, it displays an error message stating that it is "out of memory (RAM)" which is misleading and incorrect in numerous ways. I don't specifically know how Lightroom employs memory and/or temporary file space -- other than that it often uses as much virtual address space as it can get.

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

Application is not working due to memory issue

Hi Friesnds,
Kindly help me regarding settings in java. Scenario is like that. I have one server having two jboss versions (jboss-4.2.3 GA and jboss- 3.2.6). Each having java memory (JVM settings) 1 GB. The total memory of that server is 3 GB.
Problem is that every two days my application is not working due to memory issue. Once i freed the memory (through run the commands - (1). sync
(2). echo 3 > /proc/sys/vm/drop_caches
Application works fine.
I heared that the above command (echo 3 > /proc/sys/vm/drop_caches) can't run frequently because of server crash.
Kindly help me regarding this issue and provide the resolution.
Let me know if you need more information from my side.
Thanks
Ashish Shukla

All of the above. I tested on 4 different networks and had no luck, I also had friends test my network and the other networks with their iPhones and all had no issues using FaceTime.
Also after I wiped my phone (erased all content and settings) I was able to successfully initiate a FaceTime call with no changes to my network and was also able to initiate another call when connected to another previously tested network that didn't work before. Once I restored from backup though, FaceTime stopped working again.
I did find this discussion: https://discussions.apple.com/thread/5163024?start=0&tstart=0
and tried the suggestions found there too. That discussion describes my issue I am having as well.

How to correct internal memory issue

This is related to the standard SAP program SAPRCKM_MR11 in which there is one include RCKM_MR11F01 which contains a select statement :
SELECT *
     INTO CORRESPONDING FIELDS OF TABLE t_bhistory
     FROM v_ckmlgrir
     WHERE bukrs EQ p_bukrs
     AND   ebeln IN r_ebeln
     AND   ebelp IN r_ebelp
     AND   lifnr IN r_lifnr
     AND   ekorg IN r_ekorg
     AND   ekgrp IN r_ekgrp
     AND   werks IN r_werks
     AND   bedat IN r_bedat
     AND   bsart IN r_bsart
     AND   bstyp IN ht_bstyp
     AND   vgabe IN ('1', '2', '3') "Wareneingang/Rechnung/Nachbel.
     AND   loekz_k NE 'L'            "Loeschkz. Bestellkopf
     AND   loekz_p NOT IN ('L', 'S') "Loeschkz. Bestellposition
     AND ( frgrl   EQ space          "Freigabe unvollständig
     OR    frgrl   IS NULL )
     AND ( memory EQ space          "Bestellung noch nicht komplett
     OR    memory IS NULL )         "falls Feld nicht initialisiert
     AND ( xwoff   EQ space          "Wertbildung offen
     OR    xwoff   IS NULL )         "falls Feld nicht initialisiert
bei Dienstleistungsbestellungen werden mehrfach kontierte
Bestell-Pos. gegen das WE/RE-Konto gebucht, deshalb dürfen
mehrfach kontierte Pos. nicht generell überlesen werden.
      AND   vrtkz   EQ space          "keine Mehrfachkontierung
     AND   wepos   EQ 'X'            "Wareneingang wird erwartet
     AND   repos   EQ 'X'            "Rechnung wird erwartet
     AND   weunb   EQ space          "Wareneingang unbewertet
     AND   stapo   EQ space.         "Item is not statistical
There is one job FMT612P which contains this standard program and the job is going to abend
because of the select statement given above which is because of some memory issue with the internal table t_bhistory, please give us a suggestion how we can avoid the same.

Hi,
I am also facing the same issue. We had copied this report into a custom report and are trying to improve performance by breaking the view into separate queries on EKKO, EKPO and EKBE.
Can someone advise the best way to deal with this view v_ckmlgrir or a best approach to break down the view into separate queries.
Thanks
Edited by: Shreyas Shrikant Kulkarni on Jun 29, 2009 4:56 PM

Memory issue with Podcast !!!

Hi,
I have several issues with the Podcast App.
- i cannot sync podcast that i have downloaded on my laptop using itunes to the iphone,
- when i download some podcast directly on the iphone, i cannot play them, i still have to stream them,
- i have uge memory issues and i think that the downloaded version of the podcast might be somewhere on the iphone, but cannot access / delete them (over 16 GO, i have more than 4.5 GO used for 'other', that are not related to anything...)
i have tried to delete / reinstall the app, but this does not change anything...
Any help ?
Rgds

Quote
I have a MSI 975X Platinum rev 2 mb with a e6300 processor overclocked to 2.24ghz.
If your CPU operates @2.24 GHz, it means that you increased FSB frequency to about 348 MHz.
To make sure there is no misunderstanding here, let me point out the following:
Memory frequency is ALWAYS linked to FSB frequency by the FSB/DRAM Ratio you can select in BIOS. If you select 1:1 for example, the BIOS will show that memory frequency is 533 MHz. This value however, only applies to the default FSB clock speed of 266 MHz:
266 MHz x 1 = 266 MHz (or 533 MHz effective DDR2-frequency).
If your system is overclocked, what counts is only FSB/DRAM ratio, not the memory speed displayed in BIOS. That means, if you set FSB/DRAM ration to 1:1 and FSB frequency to 348 MHz, your RAM will operate @:
348 MHz x 1 = 348 MHz (or 696 MHz effective DDR2-frequency).
The main question is:
What are you talking about when you say, you can't make your RAM operate @800 MHz?
The BIOS does not offer a proper divider to get your RAM to 800 MHz @348 FSB clock speed to begin with.
You have the following choices if your overclock your system:
FSB=300 + FSB/DRAM ratio = 1.33
300 MHz x 1.33 ~ 400 MHz (or 800 MHz effective DDR2-frequency)
FSB=320 MHz + FSB/DRAM ratio = 1:1.25
320 MHz x 1.25 = 400 MHz (or 800 MHz effective DDR2-frequency)
FSB=400 MHz + FSB/DRAM ratio = 1:1
400 MHz x 1 = 400 MHz (or 800 MHz effective DDR2-frequency)
Use CPU-Z to monitor the DRAM frequency that is actually set if you are overclocking.

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).

Question for those with memory issues on k8n neo plat

I have been having issues with my memory on the k8n neo platinum board since i built the system last month and i just recently discovered a fact I had overlooked.
I Have discovered that if i test the system while it is cool (having sat turned off overnight for example), then memtest will pass the ram just fine and the system will be stable for a short period of time, generally longer if no intensive applications are used, ie. doom3 vs. websurfing).
This system, once it heats up ( seems mostly to be the nvidia 3 nb that needs to be "hot"- that is, a probe placed in contact with the module reaches about 58+ degrees c) then the system becomes unstable and memtest, if used, fails.
Prime95, if used on it when its cool, will usually take about an hour or so to fail, but if its used on the system when its been running a bit ( temps from nb at 58c+ and memory module hot to the touch) then it fails after about 20-30 seconds.
I have placed an active hs on the nb in an attempt to correct this, but temps still remain high with failures occuring.
I have spent the better part of three days testing the sytem this way and the above facts have held true in all these tests.
I have tested at stock ratings ( not using "auto" in bios, but using "approved ratings" of 10 x 200 for fsb and timings of 2-3-3-7 for my ram at 1:1 (which is recommended as well) since i am testing for base stability at this point;Voltages have been left at auto settings, however.
I was wondering if anyone else with memory issues could try this out and post if this seems to be the case for you as well.
Perhaps the memory issues on these boards are directly related to a problem with the nvidia 3 chipset running too hot?
Does anyone have a memory issue with these boards who is using water cooling on the NB ?
Lack of issues from people using 'problem" memory, but having no failures with water cooled nb's would support my assumption.

Yes i did mean chipset.
I am using a stock hs/fan from amd, which seems to run a tad hot but, considering that I wont overclock until I can get board stable, its not an issue. (runs 35-40 idle and up to 72 intensive). I need the warranty more then the extra mhz at present.
I removed the stock heatsink from the nvidia chipset and bought a generic chipset cooler (green, very little in the way of fins and seems to be aluminum) with a small fan.
I used a generic silver paste from Compusa to adhere both the cpu hs and the chipset.
I didnt lap either hs, just installed each as per instructions on artic silvers website (figured it had to go on the same way even generic).
I also bought a kingwin thermal center which i ran probes from to the cpu, case, and nb chipset.
I am not using it to adjust fans so those arent connected - its just a reference temp I can see at a glance, esp considering the funky bios reading this boards been known to give.
I assume from these responces that even a nvidia 3 250 chipset shouldnt get as hot as mine?
I asked about that from the retailer i bought this from but he seemed to think it was "ok" at 50ish celcius, but then again he didnt look too confident when he said it, lol.
Idle right now reads on Corecenter at 28 celcius for cpu and 33 celcius for the chipset, although, I have readings of 37 c and 43 c from the kingwin thermal center, which i believe to be more accurate.
My voltage reads at 11.67 for the 12v line at idle right now.
The psu i got is stick from the xblade case i bought in store. (http://www.xoxide.com/xblade2.html)
I have a dvd burner, cd drive, and two maxtor ide hd's attached to the system;The only card is the agp.
Is there a way to check and see if the cpu ispower starved? software monitor or even an external probe perhaps?
I havent put a probe on it, but the ram came in its own heatspreader, which gets very hot to the touch as well.
What temps should I be looking for on these items?

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.

Regarding Memory issues((error) while scheduling the job

Hi Friends
I am facing memory issue while rerunning BODS jobs in production.As we have rapid mart when jobs got failed i rerun the
job suddenly job got failed and in logs i found Memory issue
please help me what i have to do in steps
Thanks

I think there is no one solution to buffer pool issue. Buffer pool issue happens due to many reasons like how you design the data flow, requirement of push down or even insufficient memory in the running environment.
You can check by checking 'collect statistics for optimization' during running the job. Also in the data flow, try changing from pageable cache to memory cache by right clicking and selecting properties. The below link give some details on caching, might be helpful.
https://wiki.sdn.sap.com/wiki/display/BOBJ/CachinginDI
Arun

Memory issues while fetching content

HI all,
I am using SAP KM Apis. however i am facing some memory issues while using them.
I am using getContent() api on a resource. and then getInputStream on the Icontent object. I am using a ByteArrayOutputStream for writing the data. here is the code snippet:
byte[] buf= new byte[4096];
InputStream inputStream = content.getInputStream();
ByteArrayOutputStream os = new ByteArrayOutputStream(1024)
while ((count = inputStream.read(buf)) != -1)
    os.write(buf, 0, count);
byte[] arr=os.toByteArray();
THis code consuimes a lot of memory . we need to optimize this. we also tried removing BYteArrayOutputSteam and directly read the bytes in chunk :
int n;
do
     n = inputStream.read(buf, 0,(int)content.getContentLength());
while (n != -1);
however this approach has not helped us.
please suggest an approach where memory consumption is less and the entire content is fed.
thanks

Hi
This code worked for me for reading from a KM res...
BufferedReader reader = new BufferedReader(new InputStreamReader(is));
StringBuilder sb = new StringBuilder();
String line = null;
        try {
            while ((line = reader.readLine()) != null) {
                sb.append(line + "\n");
        } catch (IOException e) {
            e.printStackTrace();
        } finally {
            try {
                is.close();
            } catch (IOException e) {
                e.printStackTrace();
return sb.toString();
Regards
BP

Memory issues - Bring demand paging to X6.

does anyone at nokia remember a few years ago a firmware update that added demand paging to N95 and enabled the phone to do multi-tasking properly without having always memory issues? Please bring it to the X6. It's frustating to run only one app (in this case, opera mobile) and having memory warnings always poping up... After a fresh start of the phone.
In the wise words of a famous Top Gear presenter: how hard can it be?

The numbers below were constantly moving as I copied them so they're not exact but here's what task manager reported. Funny thing is that it always seems to show around 3 GB available.
Physical:
Total - 12581952 Kb
Available - 3377056 Kb
System Cache - 3237124 Kb
Kernel Memory:
Total - 204288 Kb
Paged - 143704 Kb
Non-Paged - 60056 Kb
I just saw that OEM was advising "Increase the size of the SGA by setting the parameter "sga_target" to 10752 M"

Switch memory issue

Similar Messages

Maybe you are looking for