"Allocating memory"

Hey all,
I would assume this is the first indication that the hard drive in the iPod has failed.
Basically though, my Ipod Classic gives me the "Connect to iTunes to restore" screen, so I do, and while restoring, it stops and says it's unable to do so.
I tried reformatting it in Disk Utility, and when I do, it says that it can't allocate memory and gives some bogus hard drive size (1.6 TB, to be more specific).
Any solutions/advice besides either throwing it away or sending it in to get fixed? Maybe I'm just doing something wrong.
Thanks.
Message was edited by: cwlsmith

Not possible. Post to the WOW forums.

Similar Messages

When allocating memory on stack for vm_args.options, is it safe to delete?

I am allocating memory to hold options that are passes to the JVM before calling JNI_CreateJavaVM().
Is it safe to delete the option string? i.e. does the JVM copy the option or does it just retain the pointer?
e.g.
const char* cp = loadClassPathFromConfigFile();
const char* cpSysProp = "-Djava.class.path=";
char* cpCopy = new char[strlen(classpath)+strlen(cpSysProp)+1];
strcpy(cpCopy, cpSysProp);
strcat(cpCopy, cp);
JavaVMInitArgs vm_args;
JavaVMOption options[1];
options[0].optionString = cpCopy;
// etc...
// call JNI_CreateJavaVM(...)
delete[] cpCopy; // is this safe?Edited by: Bill_Robertson_42 on Aug 10, 2008 10:44 AM
Edited by: Bill_Robertson_42 on Aug 10, 2008 10:45 AM
Edited by: Bill_Robertson_42 on Aug 10, 2008 10:48 AM

ejp wrote:
DestroyJavaVM() on the Sun VM doesn't do anything.True, but it still provides a sequence point after which the arguments passed to the JVM can be deleted, nu?I don't think so. The VM still exists.
If you call Create again it will throw as error saying that it already exists.
And you can get the existing VM via the appropriate method (whatever it is) and it still works.
So one could call it for example when exiting the application, and delete the memory then. Only real purpose then for doing the memory cleanup is to keep a memory check tool from complaining.
Conversely one shouldn't wrap the create/delete into a method that one wants to call repeatedly in the app, because it won't work.

Allocating memory to SGA

Dear Friends,
I'm in little bit confusing of allocating memory to SGA area. My server has 1024MB memory. can u tell me what are the percentage should i allocate each segment ( shared Pool, buffer cashe , Large Pool , Java Pool , PGA target )
It is grate help to me.
Regards
upul Indika.

Oracle Performance Tuning Guide has following note, same strategy can apply to other pool like shared_pool
.2.2 Sizing the Buffer Cache
When configuring a new instance, it is impossible to know the correct size for the buffer cache. Typically, a database administrator makes a first estimate for the cache size, then runs a representative workload on the instance and examines the relevant statistics to see whether the cache is under or over configured.
http://download-west.oracle.com/docs/cd/B19306_01/server.102/b14211/memory.htm#sthref485
My initial suggestion is a little aggressive, OP can lower the number according to his need.

Error allocating memory

Hello sir, There is one PC and appearing the "Error allocating memory" and when click ok then restart automatically PC So please guide the same for resolve. regards/Dheeraj/9782768993

Please post you repair question here: http://answers.microsoft.com
This forum is not for help with computer problems.
¯\_(ツ)_/¯

Freeing dynamically allocated memory

How do I free UCB dynically allocated memory at exit time? Have startup block calling allocation UCB.
Thanks,
Tim

Tim,
It depends on which function interface you are using for the UCB. There are two function interfaces. One is for use with SystemBuild only (sysbld\src\usr01.c) and makes more information available about the simulation. The other is the interface that allows you to use the same UCB for both SystemBuild and AutoCode (case\acc\src\sa_user.c).
If you are using the SystemBuild only version then there is a IINFO array that is passed to the UCB with mode information. One of the modes is LAST, which is called when the simulation is done. You can look for this mode and perform any clean up during that call. One thing with this approach is that LAST does not always get called, such as when a Interactive Simulation is aborted in the middle of a run or when a simulation is stopped in the middle by the Stop block. In those cases you would need to rely on the next approach.
When using the SystemBuild and Autocode version then you can not detect the end. However the simulation runs in its own process (simexe.exe) and so when the process is terminated any dynamically allocated memory is cleaned up. After a simulation is done simexe will remain in memory so that it can be called again if a new simulation is done with out changing the model. There are two ways to terminate the simexe process, one being to quit xmath and the other to run the command 'undefine simexe' in xmath. To make things even cleaner during the INIT mode you can check the pointers. If they are valid you can continue to use them, or free and reallocate them. If they are not valid then you can allocate the necessary memory.
For more information about UCBs and modes see the SystemBuild Users Guide chapter 14, and AutoCode Rerference Manual Chapter 2 (section UserCode Blocks).
Carl L
National Instruments

Allocated memory pool was not deleted! 1 GB memory leak is too much for me!

Dear Sirs. I found that DB environment, that was configured to use 1 GB cache size, won't free it when closed! Why? First I tried to open and close environment and got the following:
Detected memory leaks!
Dumping objects ->
{596} normal block at 0x01970040, 1048596 bytes long.
Data: < > 14 00 10 00 DB DB DB DB 0B 00 10 00 01 00 00 00
{578} normal block at 0x00397978, 464 bytes long.
Data: < > D0 01 00 00 DB DB DB DB C7 01 00 00 01 00 00 00
Object dump complete.
I have and idea that BDB will reuse the memory, rite? OK, let's try to create the same environment and open it. After environment was opened, closed, opened again and again closed, I got the following:
Detected memory leaks!
Dumping objects ->
{3663} normal block at 0x01B80040, 1048596 bytes long.
Data: < > 14 00 10 00 DB DB DB DB 0B 00 10 00 01 00 00 00
{3645} normal block at 0x00396E60, 464 bytes long.
Data: < > D0 01 00 00 DB DB DB DB C7 01 00 00 01 00 00 00
{596} normal block at 0x01970040, 1048596 bytes long.
Data: < > 14 00 10 00 DB DB DB DB 0B 00 10 00 01 00 00 00
{578} normal block at 0x00397978, 464 bytes long.
Data: < > D0 01 00 00 DB DB DB DB C7 01 00 00 01 00 00 00
Object dump complete.
So memory was not reused, nor deallocated.
By the way, you may be interested in other leak I found, but fixed, see
Replication manager memory leak when setting local site information.
This leak is more serious, I am not sure I will fix it quickly. Maybe I'm doing something wrong? Could you please suggest something?
Thanks in advance!
With regards,
Vladislav.

OK, the problem solved by fixing code in file 'log.c', method '__log_dbenv_refresh'.
Just added the code that deallocates memory of bulk buffer.
if (IS_ENV_REPLICATED(dbenv))
if (lp->bulk_buf != INVALID_ROFF)
__db_shalloc_free(&dblp->reginfo, lp->bulk_buf);
lp->bulk_buf = INVALID_ROFF;
lp->bulk_len = 0;
lp->bulk_off = 0;
It was allocated in the '__log_open' function, by the following code:
          lp->ready_lsn = lp->lsn;
          if (IS_ENV_REPLICATED(dbenv)) {
               if ((ret = __db_shalloc(&dblp->reginfo, MEGABYTE, 0,
               &bulk)) != 0)
                    goto err;
               lp->bulk_buf = R_OFFSET(&dblp->reginfo, bulk);
               lp->bulk_len = MEGABYTE;
               lp->bulk_off = 0;
          } else {
               lp->bulk_buf = INVALID_ROFF;
               lp->bulk_len = 0;
               lp->bulk_off = 0;
Sorry for time taken to read my posts, I was really needy in quick help, but solved problems myself.

Taking Resources Allocation memory reservations into account with CIQ 1.5

Hello all,
I am trying to use CapacityIQ (1.5.2) to estimate how many more VMs can fit in our environment. Unfortunately Capacity IQ appears to be estimating a _much_ larger number of available VMs (CIQ says space for 49 more VMs; Resource Allocation tab suggests room for ~1 more VM).
With the goal of having our VMs run optimally (many of them run java), we tend to use full memory reservations on our VMs, as suggested by VMware (http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1008480). This post (http://communities.vmware.com/message/1601230#1601230) suggests that CIQ does not take memory reservations into account when calculating capacity. This would be a glaring oversight by VMware; please tell me it's not correct and that there is a setting that can be changed so I _can use_ (aka continue purchasing) CapacityIQ.
thanks,
donfede

Let Mozilla know how you feel about the Plugin Check page here. <br />
http://hendrix.mozilla.org/

Oracle 10g, how to determine allocated memory is healthy or sufficient.

Hi Guys,
I have a 10.2.0.5 production database.
Currently my server has 8GB physical RAM.
3GB is allocated to the SGA and 1GB to the PGA.
Let's say one day there is a requirement from application (eg, weblogic) to increase connection pool from 20 to 50.
How are we able to know whether the memory allocated is sufficient for existing load and also the increased load?
CPU is quite straightfoward as we can generate out the cpu utilization. If utilization is low, i supposed is quite safe to increase the connection.
Kindly share ur experiences tackling such situation.
thanks

Chewy wrote:
Hi Guys,
I have a 10.2.0.5 production database.
Currently my server has 8GB physical RAM.
3GB is allocated to the SGA and 1GB to the PGA.
Let's say one day there is a requirement from application (eg, weblogic) to increase connection pool from 20 to 50.
How are we able to know whether the memory allocated is sufficient for existing load and also the increased load?
CPU is quite straightfoward as we can generate out the cpu utilization. If utilization is low, i supposed is quite safe to increase the connection.
Kindly share ur experiences tackling such situation.
thankswhat OS name & version?
is OS 32 or 64 bit?
is Oracle 32 or 64 bit?
How do you know the current RAM allocation is adequate or optimal?

Object allocations, memory and UINavigationController

I'm having a problem with object allocations
Is it possible to release/remove a view from a navigation controller stack when I click on the back button on my navigation controller? I wish to get rid of the view I just left (the one disappearing to the right of the screen). The problem is that the next time I navigate to the same view lots of new objects are allocated, and none of the old ones are released.
In the tableView:didSelectRowAtIndexPath: method I initialize a new view controller for the view I want to push to the stack and assign it to a property. The problem is that the old view seems to continue to exist in the navigation controller stack, because it's never released according to the "object allocation" section in Instruments, thus the amount of allocated objects and memory just grows and grows as I click back and forth in my navigation controller.
For example, if I click on a cell in the first table view (which displays a second view) and then click on the back button and then click on the first cell again, the second view and all of its objects are created again, but the previous instance of this view seems to still exist somewhere in the navigation controller stack.
What's the best way to solve this?
Here's some of the code in the "tableView:didSelectRowAtIndexPath:" method:
self.categoryController = [[CategoryViewController alloc] init];
self.categoryController.category = category;
[self.navigationController pushViewController: self.categoryController animated:YES];
Each time this code is executed tons of new objects are allocated, but the objects allocated by the previous CategoryViewController are not released.

Thanks you so much for the great article!!
cotton.m!!
I can cheat on my assignment again, haha!
strange
Stepwise Refinement :|
http://forum.java.sun.com//thread.jspa?threadID=5206258

How to free allocated memory

As we all know in java the memory allocated for an object is freed automatically when there is no reference for that object exist. and there is no operator in java to free the memory explicitly like delete() in c++.
But i want to free the memory allocated for the object in java for my project.
but i dont know how to do this.
Any idea abt this?

ghanoz2480 wrote:
emmmh,,,see the following documentation:
[http://java.sun.com/javase/6/docs/api/java/lang/System.html#gc()|http://java.sun.com/javase/6/docs/api/java/lang/System.html#gc()]
Edited by: ghanoz2480 on 10 Mei 09 6:58From your link:
"Calling the gc method *_suggests_* that the Java Virtual Machine expend effort toward recycling unused objects in order to make the memory they currently occupy available for quick reuse. When control returns from the method call, the Java Virtual Machine has made a best effort to reclaim space from all discarded objects. "
That does not guarantee that the gc will be run.
As the OP has already said, and as Jos has already highlighted - what the OP wants to do cannot be done in java.

De-Allocating Memory

Hello!
i'm a programmer with extensive programming knowledge about C++ and hence i know about memory management....
I have made this small little program in Java:
Class myThread extends Thread{
public void run(){
System.out.println("I RAN!!!");
new myThread().start();
Class mainClass{
public static void main(String args[]){
new myThread().start();
but the thing is, that if i run this program for a long time, it says something like memory couldn't be allocated or something like that.
all i wanna do is delete the current thread before starting the new one...
is is possible?
please help....

992452 wrote:
i'm a programmer with extensive programming knowledge about C++ and hence i know about memory management....Okay. Well, as you know, there's no direct memory management in Java.
I have made this small little program in Java:Why on earth?
but the thing is, that if i run this program for a long time, it says something like memory couldn't be allocated or something like that.What's "long time"? And what OS are you on? And what's the exact error message?
all i wanna do is delete the current thread before starting the new one...Well, you can't delete threads. Even though there's the Thread.stop() method, it's been deprecated.
What are you really trying to do? This whole mindless spawning of threads can't be what you're after (and it would be ridiculously stupid to just create new threads instead of pooling them).

[iPhone SDK] Nib vs. JIT allocation: memory pressure and programmer time

I'm going to ask a question that there's no single answer to. Instead, I'm more interested to know how different people approach the same problem.
Lately I've been finding I'm of two minds when I have a UI element or view controller that isn't always used. On the one hand, the iPhone is a fairly memory-constrained environment, and the rules for developing for it are pretty explicit: don't use memory until you need it. That suggests "just in time" or "lazy" allocation: don't allocate it until you actually need it for the first time. After that, hold onto it in case you need it again, but be ready to free it if you receive a memory warning. My code is full of methods with names like "ensureViewerLoaded" which I call just before I need the object in question to allocate it if necessary.
(For context: my applications are generally UIKit-based utility or data-browsing/editing apps with little graphical or computational complexity and very little memory pressure overall. So far, I've only released one app; at its greediest, it consumes about 1 MB. This isn't because I'm a brilliant programmer--although I do try to be parsimonious--it's just because the app doesn't need much memory to do what it's supposed to do.)
But on the other hand, allocating those same objects in nib files (or, in other cases, loading them from plists or object archives) makes me more nimble. I've found that it reduces the weight of my code, paring it down to the logic I really need to be paying attention to. That lets me code faster--which means I can modify faster and release faster. And one thing I'm finding is that on the App Store, more releases means more sales. And more sales means I get to buy a MacBook Air with an SSD sooner, and thus save my back a few pounds of strain and my patience a few seconds of compilation. ;^)
I guess what I'm asking is, how are you resolving these sorts of trade-offs? Where are you trading phone resources for programmer resources, and where are you deciding not to? And how is the type of app you're writing influencing that decision?

My applications don't need much memory either, so I let everything happen in the nib file. I typically have about three views to worry about, and nothing significantly graphical in any of them.

Java Card Memory Managament: How do you free-up allocated memory?

I have a problem with java card memory management, that causes the applet to hang. I think the java card runs out of RAM when my applet runs for several iterations or process() calls. My program requires significant size of bytes for each APDU command to be sent. (around 100-250 bytes, for each apdu.sendBytes() call).
I use a temporary byte array buffer that will contain the APDU command to be sent, declared as:
private byte [] tmpBuff;Before each process() call, the tmBuff is initialized and contains a new byte array containing the APDU command to be sent. (array size around 100-250 bytes).
tmpBuff = new byte[] {0x00, ... } On the process() call, the tmpBuff is copied to APDU and sendBytes() function is called. The tmpBuff byte array is reinitialized after every process() call to contain the next command. After about 20 successful commands by the process() call, the applet seems to ran out of RAM and hangs.
I suspect, that when tmpBuff is reinitialized before each process() call, the Java Card garbage collector does now free-up the memory that was used for the previous tmpBuff byte array initialization.
Is there a way to reclaim the memory allocated for tmpBuff after it has been initialized?
Or maybe call the Java card garbage collector?

Cenon,
Generally speaking, the new keywork is a bad idea outside the install method or constructors as the JCRE is not guarenteed to have a garbage collector (and if it does, has to be called explicitly by JCSystem.requestObjectDeletion(); This however is slow.
A better option may be to use memory more efficiently than to rely on garbage collection. A way of doing this would be to have an instance variable that is initialised once and reused. This allows you to use either a transient or persistent array.
public class TestApplet extends Applet {
    private final static short BUFFER_SIZE = (short) 300;
    private final byte[] buffer;
    private TestApplet() {
        // only have one of the following not commented out
        /* persistent buffer */
        // buffer = new byte[BUFFER_SIZE];
        /* transient buffer (much faster) */
        buffer = JCSystem.makeTransientByteArray(BUFFER_SIZE, JCSystem.CLEAR_ON_DESELECT);
    public static void install(byte[] bArray, short bOffset, byte bLength) {
        // GP-compliant JavaCard applet registration
        new TestApplet().register(bArray, (short) (bOffset + 1), bArray[bOffset]);
    public void process(APDU apdu) {
        // Good practice: Return 9000 on SELECT
        if (selectingApplet()) {
            return;
        // do some work here with buffer
}In the above code you would be able to use the buffer to build the command and you will not have a memory leak.
Cheers,
Shane
Edited by: safarmer on Jul 8, 2008 12:25 PM

Allocating memory to integrated graphics card [resolved]

I recently acquired a dell dimensions 2350 with an integrated 82845G/GL[Brookdale-G] GPU. The GPU has no video memory of it's own, but robs it from the main system RAM. From Dell's website:
Between 32 and 64 MB of system memory may be allocated to support graphics, depending on system memory size and other factors.
Since I've maxed out the system memory at 1gig, I'd like to make sure that the GPU is getting the full 64 megs. I thought I could verify this easily by just running htop, and seeing how much memory the system claims to have, thinking that total system ram minus what htop reports would be how much memory is allocated to the GPU. However, htop reports a total of 1010 megabytes. That led me to believe that just 14 megabytes were allocated to the GPU. Is that wrong? Is that missing memory, memory eaten up by the kernel or something?
I tried forcing X to grab more memory by entering "VideoRam 65536" in /etc/X11/xorg.conf under section "device" along with my driver information, but that changed nothing, and the X log file says:
# cat /var/log/Xorg.0.log | grep -i videoram
(WW) intel(0): VideoRam configuration found, which is no longer recommended.
(II) intel(0): Continuing with default 131072kB VideoRam instead of 65536 kB.
(**) intel(0): VideoRam: 131072 KB
That doesn't make sense to me either, since according to Dell, the max allotable video ram would only be 65536.
Thanks in advance.
P.S. The display is fine, and GLX reports that DRI is enabled, but glxgears is ridiculously low, and scrolling in a terminal emulator can be slow sometimes (although scrolling in a web browser is fine). glxgears reports about 835 fps.
Last edited by Convergence (2008-10-01 07:12:40)

Thanks for the responses guys.
Adam: I think that you might be right, that Dell wasn't planning on people using linux drivers, and therefore listed limitations that the windows drivers might enforce. As for the slow scrolling, I alleviated the problem a little by switching to LXterminal, but it's still annoying. You'd think that it would be a lot less processor intensive to scroll text in a terminal, as opposed to graphically enriched hypertext in a browser window. Weird.
Square: I don't really have a problem, (except for scrolling in a text emulator). I just want This old thing to perform as well as possible (partly to show off to the guy that used to own it.) I had a little trouble playing Chromium at first, but one of my tweaks fixed that at some point. What do you mean that it used to be controlled by the bios, but was removed? You mean that at some point the driver developer (i810) decided to override control of videoram from the BIOS?

Get mails from server and put into DB without allocating memory.

Hi all
I have a application that downloads the mails from the mail server and then write them to the DB.
I am using folder.getMessage method to get the mails from server.
is there a way using which I can have a function that acts as a pipe between my server and DB and write the mails without consuming the memory.
(may be something to do with getInputByteStream/getOutputByteStream or getInputStream and setBinaryStream 'preparedStatement interface ')
Thanks

Hi all
I have a application that downloads the mails from the mail server and then write them to the DB.
I am using folder.getMessage method to get the mails from server.
is there a way using which I can have a function that acts as a pipe between my server and DB and write the mails without consuming the memory.
(may be something to do with getInputByteStream/getOutputByteStream or getInputStream and setBinaryStream 'preparedStatement interface ')
Thanks

"Allocating memory"

Similar Messages

Maybe you are looking for