Memory issue on replica client

I am using bdb 4.7.25 on freebsd 7.0 C++ api.
I have applied patch from Link: Re: Question on replication error like "DB_ENV->rep_process_message: DB_NOTF.." to fix log_archive issue. I have also applied the patch suggested in the reply to above message.
On master node, I am doing lot of write operation with periodic checkpointing.
Case 1:
=======
Later, when master node archives (deletes) log files after checkpointing, after few minutes of transaction, I get following error on client node.
Log sequence error: page LSN 0 0; previous LSN 25 1048356
Recovery function for LSN 26 4263441 failed on forward pass
Client initialization failed. Need to manually restore client
PANIC: Invalid argument
DB_ENV->rep_process_message: DB_RUNRECOVERY: Fatal error, run database recovery
message thread failed: DB_RUNRECOVERY: Fatal error, run database recovery
PANIC: fatal region error detected; run recovery
DB_ENV->rep_process_message: DB_RUNRECOVERY: Fatal error, run database recovery
message thread failed: DB_RUNRECOVERY: Fatal error, run database recovery
PANIC: DB_RUNRECOVERY: Fatal error, run database recovery
PANIC: DB_RUNRECOVERY: Fatal error, run database recovery
Please advice, what could be possibly wrong and how can I fix it?
Case 2:
=====
On similar instances, when I dont do log_archive'ing on master node to delete the log file, the memory footprint of client process periodically increases a lot and then decreases back to normal. I suspect this happens around the checkpointing, where master sends burst of messages to client to replicate. But gradually the footprint increases too high and starts using swap space and there is not enough memory to allocate. Is this fluctuation of memory footprint on client node an expected behaviour?
Potentially following output for db_stat-4.7 -MA might help.
This is the statistics from the replica client node machine.
Mpool REGINFO information:
Mpool Region type
3 Region ID
__db.003 Region name
0x28710000 Original region address
0x28710000 Region address
0x287100c0 Region primary address
0 Region maximum allocation
0 Region allocated
Region allocations: 4094 allocations, 12894388 failures, 4007 frees, 1 longest
Allocations by power-of-two sizes:
1KB 34
2KB 1
4KB 0
8KB 12898447
16KB 0
32KB 0
64KB 0
128KB 0
256KB 0
512KB 0
1024KB 0
REGION_JOIN_OK Region flags
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
MPOOL structure:
9 MPOOL region mutex 2 / 26M 0% 11489 / 674238720
401 / 2533580 Maximum checkpoint LSN
37 Hash table entries
11 Hash table last-checked
496749207 Hash table LRU count
497385622 Put counter
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Please help me resolve both cases.
Regards,
Sury

Thanks very much! It's long, Is there an rignt <font face="tahoma,verdana,sans-serif" size="1" color="#000">answer</font> for the problem?

Similar Messages

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

Plus Memory Issues

Hi all.
Oracle Business Intelligence Discoverer Plus 10g (10.1.2.45.46c)
Windows 2000 professional Client
I've been making few tests here using Oracle Disco Plus. We use Oracle Portal to present dashboards for end users. Whenever they need analytic capabilities, there's a link to Discoverer Plus in the main page.
I've selected to launch Plus, and checked memory consumption using Windows Task Manager. Then I can see IEXPLORE.EXE process is consuming around 77MB after running a simple query.
When I close Discoverer, using FILE -> EXIT menu option, the IEXPLORE process still consumes the same amount of memory. So, when end-users close Oracle Discoverer, the memory ramains allocated as if you still have Disco Plus opened. This is not a big problem for me cuz my client machine has 1.5 gb RAM. But most end users machine have between 256mb and 512mb. If we sum the memory discoverer consumes with all of that fancy blinking software end-users love to install in their env., I believe they'll have performance issues using Oracle Discoverer.
Why Discoverer does not free used memory when we exit it? Is there any misconfiguration in the Java Virtual Machine or server parameters?
Regards,
Marcos

Hi Marcos
If you are running Discoverer 10g Plus on machines with 256mb or 512mb your users are going to be very, very disappointed. Those machines are heavily underpowered for running the Discoverer Plus applet.
Appendix A of my Discoverer 10g Handbook is a questions and answer session. The following question and answer comes from there:
QUESTION: We are running Discoverer Plus. How much memory do you suggest individual PCs should have? We are strictly using Discoverer Plus and Viewer and find the performance to be really slow.
ANSWER: Your question concerning memory on the client is most interesting. Even though Plus and Viewer are web-based applications, the amount of memory available on the client does make a significant difference. I used to say that 512mb was needed but I have personally come across performance issues at a client whose machines have that amount of memory. My own laptop, which has 2Gb of RAM has no such issues. I will therefore be recommending a minimum of 1Gb from now on with an optimum of 2Gb. If you can possibly afford it, your new Plus machines should have at least 1Gb and be capable of being expanded to 2Gb should the need arise. Of course, if you can get 2Gb to begin with you will have far fewer issues.
My own experience at dozens of clients suggests that each Plus connection will take an average 85mb of space, so with your machines coming in at 77mb this is 100% normal activity and is to be expected.
Now other issues arise because of this in that the standard Java install sets the memory allocation to 64mb which means that in nearly all cases you will be paging to disk! Now the cache size on disk is also low by default, being a miserly 50mb. I've therefore sometimes had the need to alter my Java settings to allocate extra memory. If you ever find you need to adjust the memory settings this may help:
If using JInitiator:
To increase the maximum heap memory, use this workflow:
From the Start button, use Settings | Control Panel
Double-click the JInitiator 1.3.1.22 Plug-in
On the Basic tab, set the Java Runtime Parameters to: –Xmx256m
Click Apply
This sets the maximum amount of memory to allocate to Java to be 256mb. You can alter this to a higher value if you have plenty of memory. For example if you have 2 Gb memory you could try using –Xmx512m. Generally I would not set the maximum to be more than 50% of your system memory.
To increase the cache allowed for your local JInitiator, use this workflow:
From the Start button, use Settings | Control Panel
Double-click JInitiator 1.3.1.22 Plug-in
On the Cache tab, set the Maximum to 500mb:
Click Apply
To increase the maximum heap memory, for the Sun Java client, use this workflow:
From the Start button, use Settings | Control Panel
Double-click the Java Plug-in
On the Advanced tab, set the Java Runtime Parameters to: –Xmx256m
Click Apply
To increase the cache allowed for your local Sun Java, use this workflow:
From the Start button, use Settings | Control Panel
Double-click Java Plug-in
On the Cache tab, set the Maximum to 500mb:
Click Apply
By the way, you also should not allow the Java client to automatically update itself as this will cause issues too when the client Java is running a higher version than the server Java. This posting on my blog explains:
http://learndiscoverer.blogspot.com/2006/06/10g-discoverer-handbook-page-923-do.html
As for memory not being cleared out properly, this is typical. Once the applet has loaded it remains loaded which is why the next time you launch Discoverer Plus it opens much faster. This is another reason why 256mb or 512mb would be considered underpowered.
I hope this helps
Best wishes
Michael Armstrong-Smith
URL: http://learndiscoverer.com
Blog: http://learndiscoverer.blogspot.com
P.S.
As previously mentioned, appendix A of my Discoverer 10g Handbook is a Q&A section listing many of the answers to questions that are found in this forum. I, and Oracle, are always a little surprised by the number of people who don't have a copy. After all, it is the official Oracle Press book on the subject.
I mention this, not as a criticism of yourself, but for the hundreds of folks who might read this posting to let them know that many of the questions they would ask are in the book, and in much more detail than can be posted here, especially when pictures and screenshots are required.

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"

IPod Nano 5th Gen memory issues?

Hello. My iPod Nano 5th gen is great, and I've been able to use it for 2 years now, and it serves me well. Perfect condition since the day I got it. However, there are some memory issues...
First off, I have only two recorded videos totaling 1 minute and 29 seconds, so it shouldn't take up much memory at all. And I don't have any other videos on my iPod either.
Well, when I go to "About" under "Settings", then it always says that there are only 902 MB left, and it's an 8 GB. What's weirder is that it says that 6.1 GB are being used my audio, and I only have 712 songs. When I select all of the songs that are on my iPod on my PC, then it tells me that it totals to only 3.53 GB. Kinda weird, and I really need this extra space now.
Secondly, I should tell you that I don't use iTunes to syncronize my iPod. I use a third-party program called CopyTrans Manager because it's simpler, easier to navigate, and faster in my opinion. Idk what it is, but it's bothering me. Hopefully some of you can tell me where I can go to eliminate these issues and finally get my iPod back to better use and full memory.
Help me please. I don't know where to go next...
Thankee.

I don't use iTunes to syncronize my iPod. I use a third-party program called CopyTrans Manager
Contact the manufacturer. Check with them to determine if the issue is with them.

Memory issues in java3d1.2(openGL ver) and 1.2.1-03 sdk(openGL ver)

hi ,
i am working in java 3d and handling memory issues .I have made following observations.
In java3d 1.2 version,when we close a primitive ,(transform group,point3d,transform 3d release) about 80% of memory used by the primitive when it was opened.but point4d releases only 2% of memory.
on a contrary when i use java3d1.2-03 sdk point4d releases about 75% of memory and others(transform3d,transform group,point3d ) releases about 40% of memory allocated to them.
can somebody tell me if there is some kind of difference in these two versions related to memory?or is there any memory bug in the later version?
thanks
sangeeta

hi,
We r using memory management tools like Jprobe and optimizer IT to count the rate of memory released.
Thanks
sangeeta

IDCS4 V6.0 memory issue with preflight

When I create a custom profile for preflight and run it i encounter memory issue. Hard disk starts running indefinitely and after a while InDesign crashes. I have try, by steps, to make the profile less demanding (I should try the reverse way) but instead of crashing, indesign finally sends memory error message and can crash later. Apple Activity monitor shows that sometimes indesign requires all the memory available (1,5Go)
Any of you have ever try to set a custom preflight profile ? The basic one is really too tolerant.
Thank you.
I'am on Imac 3,06 2 Go

I've spent quite a bit of time working with custom preflight profiles on my MacBook Pro, 2 Gb memory, Mac OS X 10.5.5. I have never run into a memory error. In fact, I've never ever run into a memory error in InDesign. Memory errors can occur because of defective fonts. Have you tried with different fonts? Have you tried on a different computer?
Yes, the [Basic] preflight checks only for missing fonts, missing or modified graphics, and overset text. You need to work with custom preflight profiles depending on your particular workflow.

Memory issue on replica client

Similar Messages

Maybe you are looking for