Memory Alloc rises when dragging iPhone Simulator

I have detected a weird behaviour of the memory allocation of my App.
When the app did finish launching, if then I drag the SIMULATOR window when the app is running, the memory curve rises.
This phenomenon appears ONLY ON THE FIRST DRAG.
http://img374.imageshack.us/my.php?image=image2lo9.png
Check the curve and white arrow.
Do you have any idea what this means ?

I have to precise that I am not using the accelerometer.
I have no movement detection implemented.
I am just waiting the user to tap the screen one time to go to next screen.

Similar Messages

"Memory Allocation Error" when Building a DVD

Hi all!
I have a problem. When I start to build a DVD. Encore stops with a "memory allocation error". The project I tried to build is 3.06 GB, so it's must fit to a simple DVD. My HDD has enought free space.
I tried to build it on two totally different computers but the error is the same. I didn't find any answer for this error. Can anybody help me?
I use Encore CS4, and the project is made in Premiere Pro CS3.
The computer #1:
Windows Vista (but I tried also with XP)
1 GB RAM
250 GB HDD
The computer #2:
Windows Vista
2 GB RAM
160 GB HDD

I get the same! I was having an issue with video files from my digital camera, so I opened up Premiere CS3, which took them in and encoded them to MPEG-2 just fine (tisk-tisk! Premiere and Encore CS4 both failed to play them or encode them properly!!!)
Them I put these MP2 files into a project which has 2 menus, 4 video timelines, 2 slideshows with 200+ images and some background audio files (one linked to a menu, another plays in sequence after first finishes). The project is for PAL screen, and it is 4-some Gb, but less than a disk. I have 4Gb of RAM and 6Gb of page file, 70Gb free on my HDD. Running Vista Ultimate x64.
Slideshows render, and videos do not require transcoding, so the project is ready to build, it starts writing the ISO file, and crashes after 1.8-1.9Gb is written.
There seems to be no easy way to re-create my slideshow, or I would have just re-built the entire Encore file to see if that would work.
My PC is overclocked, I admit, I have not tried it without an overclock, but my system has been uber-stable for 12+ months! I will try and report if it fixes anything, but I doubt it. I have also tried to run this build after a fresh reboot with mostly everything turned off, to prevent system conflicts. If that's what it is, I must have missed something. But Encore CS4 is BUGGY LIKE GOD KNOWS WHAT!!!!! This is one crash I can't get around, but it's not the only one I've had. If anyone knows an answer, PLEASE post it here! Adobe guys please please please please! My project's already held up for a month!

Memory allocation error when burning in premiere elements 2

I have premiere elements 2. I happily burnt a version of my dvd then suddenly it stopped burning and I had the above message during the burning section of the process. My computer has adequate memory to run this programme and nothing new has been added. I then downloaded Premiere elements 7 as a trial and burnt this Dvd yesterday. However today it won't burn through 7 either so i am reluctant to upgrade unnecessarily. Can anyone shed light on why I receive this error message.
Other things seem to burn but I am beginning to receive messages that Adobe is low generally on memory allocation.
Regards
Erika

memory allocation error when burning in premiere elements 2
Erika Lindsay - 09:30am Jan 4, 2009 Pacific
I have premiere elements 2. I happily burnt a version of my dvd then suddenly it stopped burning and I had the above message during the burning section of the process. My computer has adequate memory to run this programme and nothing new has been added. I then downloaded Premiere elements 7 as a trial and burnt this Dvd yesterday. However today it won't burn through 7 either so i am reluctant to upgrade unnecessarily. Can anyone shed light on why I receive this error message.
Other things seem to burn but I am beginning to receive messages that Adobe is low generally on memory allocation.
Regards
Erika

Memory Allocation problem when using JNI

For a Project we need to interface Labwindows-CVI/ Teststand with an application written in Java. we are using JNI. The code uses JNI_CreateJavaVM to start a JVM to run the Java interface code. The code did run for some time , but now ( without any obvious change nor on the CVI side neither on the Java side) JNI_CreateJavaVM fails with -4 error code, that means that the start of the JVM failed due to memory allocation failure. First investigation showed, that even if Windows Task Manager shows about 600M free physical memory, you can allocate in CVI only about 250M as a single block at the time we are calling JNI_CreateJavaVM. That might be a little bit to less as we need to pass -Xmx192m to the JVM to run our code. Unfortunately just increasing the physical memory of that machine from 1.5G to 2G doesn't change anything. The free memory showed by Task Manager increases, but the allocatable memory block size does not. Are the any trick to optimize CVI/Teststand for that use case ? Or maybe known problems with JNI ?
Solved!
Go to Solution.

hi,
have you tried other functions to allocate memory?
the -Xmx command only sets the maximum heap size. You can try to use -Xms. This command sets the initial Java heap size.

Static memory allocation

Hi,Consider the code shown,
1. class A{
2.
3. public static void main(String ... args)
4. {
5. int m;
6. m = 30;
7. }
8. }
Execution of which line allocates a memory for 'm'?

Now if you change the code to
public class Test {
     public static void main(String... args) {
          int m=30;
}you would get
javap -c Test
Compiled from "Test.java"
public class Test extends java.lang.Object{
public Test();
Code:
   0:   aload_0
   1:   invokespecial   #1; //Method java/lang/Object."<init>":()V
   4:   return
public static void main(java.lang.String[]);
Code:
   0:   bipush 30
   2:   istore_1
   3:   return
}which is the same.
The idea is that it doesn't make a difference how you write it. Memory allocation happens when is decided after the JVM optimization and not your written code.

[iphone sdk] memory allocations and application sandboxing

folks,
does the os automatically de-allocate any memory allocated when my app exists? reason i ask is the phone seems to get slower and slower over time with more crashes. a hard restart seems to fix the problem.
i'm guessing that it is because i'm not cleaning things up on exit or something, but maybe there is something else wrong.
john

The academic answer is: It shouldn't matter how much memory you leak in your app after the app has been closed. I can't speak to how the device functions cause I can't test on one yet! But it's UNIX under the hood and that means each process is assigned it's own address space. Any memory allocated to a process is completely reclaimed when the process exits.
I'm not sure what changes Apple made to the VM kernel subsystem for the iPhone. Unix is already tried and tested in this arena -- so if it's the default Darwin VM I would be very surprised if this is a bug. But since this is embedded they may have added some "shortcuts" for performance and efficiency... hard to say. Since you have the device, are you able to do any system level diagnostics? does the device lose free memory the more your start/stop your app?
Also -- the device has 128MB of RAM. The 8 or 16GB is storage, which isn't used for RAM. The specs are hard to find, but I think I found the answer through Google on the amount of RAM in the iPhone and iPod Touch.
Cheers,
George

When I view my phone capacity, there is an amount of memory allocated to "other"...what is this?

When I view my phone capacity, there is an amount of memory allocated to "other"...what is this?

depends on what data occupies your Other category on your iPhone and whether you could/want to delete it or not.
Check your Camera Roll for lots of photos or shot videos, you can get rid of some which you consider wortty deleting. Regarding data allocated to each of your apps - this can vary and you can check that as described by John above. You can uninstall the apps on your iPhone you consider worth removing - this will remove their app data too.

When syncing iOS devices to iTunes, the memory allocations shown in iTunes are all over the place

There must be threads about this, but apologies for my inability to find any.
As the title says: I plug my iPhone or iPad into my iMac, and when I look at the memory allocation as displayed in iTunes, 6GB or whatever are free. Then I sync again, and suddenly 8GB are free. Sync again, and now 2GB are free - even though nothing has changed. I get this with both iOS devices.
Additionally, often what iTunes shows has no relationship to what the device says when I go into Settings: last week iTunes believed there were 0GB in Photos - because after all I had erased them! - but the iPad recorded 25GB, somehow.
Is this a known issue, or is something screwy with my system?
Thanks in advance!

Thanks, but that's not really the issue. I do manage it manually - I've got a lot of smart lists, smart photo albums, and so on, all set up to sync with the iOS devices.
The problem is that the iPhone/iPad memory, as displayed in iTunes when the device is plugged in, seems to be very inaccurate and variable. When I plug the iPhone or iPad in, iTunes tells me (for example) that, with current settings, 5GB will be free. It syncs, and then suddenly 2GB are free. I sync again - changing nothing, so there should be no change in memory allocation - and suddenly 6GB are free. Somehow, despite syncing no books at all, there's a bizarre 60MB "Book" that iTunes tells me is sometimes on the iPhone, and sometimes not. That little stretch of purple just suddenly appears some days.
At times it tells me it's too full and can't sync at all. So I wipe, for example, 6GB off the "too full" iOS device, and after doing that suddenly 10GB are free, so I put the 6GB back on no problem. And after I add that 6GB back on, maybe there are 8GB free, or maybe 2GB, or maybe 4GB. In my world, 10GB-6GB=4GB, but iTunes is using quantum arithmetic or something.
Wiping a lot of photos off was great fun. I had iTunes unsync and remove all photos - so, in that line at the bottom, all the photo memory allocation disappeared. Cool. Mission accomplished. Then I clicked to another tab in iTunes, and suddenly the photo memory jumped back up to 15GB. Looked back in the Photos tab - nope, I'd told it to sync no photos at all. Checked the iPhone itself: oh, neat. 25GB of photos, despite not syncing any. Eventually, after repeating the process several times, all the photos were eventually gone, but the whole process was bizarrely complicated.
Basically, when I plug the iPhone or iPad into iTunes, iTunes seems to have no idea what the memory allocation actually is - which occasionally makes syncing complicated.
It's not a giant issue, but it's quite annoying - and I'm wondering if this is just me, or if this is a common issue. I think this issue may also be discussed in some of the "can't delete songs" or "can't delete photos" threads, but some of those threads are so long and cover so many different problems that they're kind of hard to read.

Bug report & possible patch: Wrong memory allocation when using BerkeleyDB in concurrent processes

When using the BerkeleyDB shared environment in parallel processes, the processes get "out of memory" error, even when there is plenty of free memory available. This results in possible database corruption.
Typical use case when this bug manifests is when BerkeleyDB is used by rpm, which is installing an rpm package into custom location, or calls another rpm instance during the installation process.
The bug seems to originate in the env/env_region.c file: (version of the file from BDB 4.7.25, although the culprit code is the same in newer versions too):
330     /*
331      * Allocate room for REGION structures plus overhead.
332      *
333      * XXX
334      * Overhead is so high because encryption passwds, replication vote
335      * arrays and the thread control block table are all stored in the
336      * base environment region. This is a bug, at the least replication
337      * should have its own region.
338      *
339      * Allocate space for thread info blocks. Max is only advisory,
340      * so we allocate 25% more.
341      */
342     memset(&tregion, 0, sizeof(tregion));
343     nregions = __memp_max_regions(env) + 10;
344     size = nregions * sizeof(REGION);
345     size += dbenv->passwd_len;
346     size += (dbenv->thr_max + dbenv->thr_max / 4) *
347         __env_alloc_size(sizeof(DB_THREAD_INFO));
348     size += env->thr_nbucket * __env_alloc_size(sizeof(DB_HASHTAB));
349     size += 16 * 1024;
350     tregion.size = size;
Usage from the rpm's perspective:
The line 346 calculates how much memory we need for structures DB_THREAD_INFO. We allocate structure DB_THREAD_INFO for every process calling db4 library. We don't deallocate these structures but when number of processes is greater than dbenv->thr_max then we try to reuse some structure for process that is already dead (or doesn't use db4 no longer). But we have DB_THREAD_INFOs in hash buckets and we can reuse DB_THREAD_INFO only if it is in the same hash bucket as new DB_TREAD_INFO. So line 346 should contain:
346     size += env->thr_nbucket * (dbenv->thr_max + dbenv->thr_max / 4) *
347         __env_alloc_size(sizeof(DB_THREAD_INFO));
Why we don't encounter this problem earlier? There are some magic reserves as you can see on line 349 and some other additional space is created by alligning to blocks. But if we have two processes running at the same time and these processes end up in the same hash bucket and we repeat this proces many times to fill all hash buckets with two DB_THREAD_INFOs then we have 2 * env->thr_nbucket(37) = 74 DB_THREAD_INFOs, which is much more than dbenv->thr_max(8) + dbenv->thr_max(8) / 4 = 10 and plus allocation from dbc_put, we are out of memory.
And how we will create two processes that end up in the same hash bucket. We can start one process (rpm -i) and then in scriptlet we start many processes (rpm -q ...) in loop and one of them will be in the same hash bucket as the first process (rpm -i).
I would like to know your opinion on this issue, and if the proposed fix would be acceptable.
Thanks in advance for answers.

The attached patch for db-4.7 makes two changes:
it allows enough for each bucket to have the configured number of threads, and
it initializes env->thr_nbuckets, which previously had not been initialized.
Please let us know how it works for you.
Regards,
Charles

Memory allocation when using multiple instances of a static array.

Hi,
I have question regarding the amount of memory allocated using multiple instances of a class that has declared a static array, e.g.:
package staticTest;
import javacard.framework.*;
public class StaticClass
     static byte[] staticArray;
     public StaticClass()
          staticArray = new byte[100];
/* Another class */
package statictest;
import javacard.framework.*;
public class MyApplet extends javacard.framework.Applet
     StaticClass staticLibA, staticLibB;
     public MyApplet()
          /* Here we use two instances */
          staticLibA = new StaticClass();
          staticLibB = new StaticClass();
     public static void install(byte[] bArray, short bOffset, byte bLength)
          (new MyApplet()).register(bArray, (short)(bOffset + 1), bArray[bOffset]);
     public void process(APDU apdu)
          byte[] buf = apdu.getBuffer();
          switch(buf[ISO7816.OFFSET_INS])
}When downloading and installing this applet on a gemXpresso 211 PKis (that has a ' Get free EEPROM memory' function) the card reports that the amount of memory is increased by a approx 100 bytes every time a new staticLibX is added in the MyApplet constructor. Is this correct? If yes, can someone explain to me how to declare a static array that only allocates memory once and are being shared by the instances.
Best regards,
Jonas N

Hi!
I have another issue about static variable. The following is my sample code:
========================================
package com.Test01;
import javacard.framework.*;
import javacard.security.*;
import javacardx.crypto.Cipher;
public class Test01 extends Applet {
     OwnerPIN Pin;
     static DESKey[] keys;
protected Test01(byte[] buffer, short offset, byte length) {
keys = new DESKey[4];
length = 0;
while (length < 4) {
     keys[length] = (DESKey)KeyBuilder.buildKey((byte)3, (short)0x80, false);
     length = (byte)(length + 1);
public static void install(byte buffer[], short offset, byte length) {
new Test01(buffer, offset, length);
===========================================================
If there are two instances, A and B, created in the package.
My issue:
1. Are keys[0]~ keys [3] kept while B is deleted?
2. Does each instance have itsown object while "keys[length] = (DESKey)KeyBuilder.buildKey((byte)3, (short)0x80, false);"?
3. follow item 2, if A and B share the same object, is the object kept while B is deleted?
Thank you
Best regards,
kantie

Large iPhone "Other" Memory Allocation

My iPhone 4 (iOS 5.1) is showing that I have 0.80GB of memory allocated to "other." I only have 0.17 GB of audio, 0.39 GB of apps, and 1.38 GB in photos (over iCloud) on it at this time. I've cleared call and web history, texts, cookies, bookmarks, deleted my e-mail accounts and basically tried to isolate any high usage items, but no joy. What in the wide world of sports is taking up all of this space, and how can I get rid of it? It seems excessive considering the actual content of my phone...

DiskAid is a transfer tool for iPhone, iPad, and iPod. It is available for both PC and Mac platforms. It will allow you to see pretty much everything that is on your iPhone. Once you have DiskAid installed go ahead and plug in your iPhone and make sure you back it up. Now go ahead and open DiskAid. On the far left you will see a bunch of different icons. Click on File System, they may be a box that pops up that asks you if you know what you are doing. Just click ok because we know what we are doing here. Now click on Media, then iTunes_Control, then Music. You will see a bunch of folders (like in the photo below), go ahead a delete them all.
You will notice the size of “Other” has dropped dramatically!
Read more at

Hi, I finally got lucky and past the "other" memory status issues when syncing. Now I'm "waiting for changes to be applied" sync stuck all night (itunes yesomite iPhone 6 plus). is this a bug? I have not had a single successful sync with yesomite.

hi, I finally got lucky and past the "other" memory status issues when syncing. Now I'm "waiting for changes to be applied" sync stuck all night (itunes yesomite iPhone 6 plus). is this a bug? I have not had a single successful sync with yesomite.
please help. this issue prevents music from syncing. I have set the sync setting to convert songs to 192kbps AAC to save space, I figure that could slow the sync
down, but it's hanging indefinitely (I've left it for 24 hours with out it completing.)
the the only music that appears on the phone are songs purchased from the iTunes Store. 95% of my collection are rips from my CDs.
thank you for any help!

Yeah it's pretty sad that $1000 phone they put out you such cheap memory It causes issues, I have iPhone 6+128 GB actually this is the second brand-new one they gave me because they keep affording it trying to act like that's not the issue because they're too stupid to know how to check what memory is in each one before they give it to me when I have told them multiple times my back up runs perfectly fine on two 5s phones and a 6 64GB of course running MLC memory.
I told them it's because just like the write ups say I have 809 apps but I have not even put all my music on the phone so I'm still running 50 to 60 gigs free and it crashes and reboots itself sometimes in multitasking and more often than it does that in between multitasking I get a black screen for 1 to 2 seconds in between apps and upon start up the Apple logo screen will flicker and do weird things, One of the genius idiots asked me if I could just delete some of my apps, really that's the answer to fix the phone the customer needs to limit the amount to apps they put on their phone, why the **** get a 128 gig if you can't put on anything you want to it guess they need to start selling them saying you can only put a limited number of apps on them, it's really is a **** joke, I have over $20,000 of Apple merchandise easily and always get the new phone every year but I'm starting to reconsider my decisions in the future because this company is starting to go downhill, The reason water not recalling the phones is because they're dealing with their top-of-the-line thousand dollar phones in this case and most people don't have over two or 300 apps so they're not having as many issues, so basically they have messed up phones they just don't know it in their hands and Apple is just too **** greedy to recall the phones, they'd rather sell customer spends that only work half ***.
Stuff like this will be the downfall of their company, all the people that stay with them because as long as you don't jailbreak their stuff it normally just works without issue will be soon jumping ship if stuff like this keeps up, because I can guarantee they got me thinking now.
not that I wanted to know or should I be expected to but I even offered for them to open up my brand-new phone and just replace the memory to MLC memory which is something I shouldn't have to do with a brand-new **** phone, they should just make one with the right memory and give me a new phone, actually just don't sell customers that buy the top-of-the-line phone from you trash ones in the first place that would be a great option.
what burns me up the most is when you talk to AppleCare and Genius Bar they try to act like the issue isn't there and they're unaware of it, they say that Apple hasn't come out with any information about it, yeah that's because they don't want to recall the trash.
Apple has became nothing better than your run-of-the-mill company, android is becoming just as good as they are sad to say this since I have been an Apple fan for so long but there is no excuse for BS like this they have been looking for options to fix my phone for a month now this is not the way you should treat loyal customers, I would've been better off keeping my 5S and in the future just switching to android.
it's pretty sad that the company has no idea how to check which memory is in their **** phone and even after I offered to let them just replace the memory in my new phone by opening up my brand-new phone to replace it they have no idea how to do that either, yeah Genius Bar sure, I think that should change the name to idiot bar and Apple don't care instead of Apple care.

Error: cc1obj: out of memory allocating 1130584464 bytes after a total of 0

hi guys : )
I have a weird bug. It's a compile time error but only happens when i compile in release config. when i compile in debug mode, my app runs perfectly. when i compile in release mode (even to simulator) i get this error:
cc1obj: out of memory allocating 1130584464 bytes after a total of 0 bytes
Command /Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin/gcc-4.0 failed with exit code 1
any one else seen this?

the file was too big : )

IOS app crashes on return from cameraUI - a memory allocation problem?

hey all
trying to finish my first app
when running on iOS, the app SOMETIMES crashes after returning from cameraUI (either "use"/MediaEvent.COMPLETE or "cancel"/Event.CANCEL).
when i exit some other running apps on my iPhone 3Gs (and not that many are open), the problem goes away, which makes me think this is some memory allocation problem
in that aspect, can i trust the iOS to exit inactive applications to allocate more memory for my, currently active, AIR app?
(there is no memory leak)
this is an iPhone 3Gs running os version 4.3.5
the app was made with Flash Pro 5.5 overlayed with the AIR 3.1 sdk, and deployed using the "deploy for app store" type (which should be the most bug-free)
(no crashes on Android or desktop versions)
anyone had this cameraUI problem or a similar one where an app crashes if more then some numbers of apps are open?
thanx
Saar

I don't get this. Its beyond frustrating:
we are not talking about using an uncommon phone capability, access to a phones camera is about the most basic native level of access you would be looking for in a mobile framework
we are not talking about an edge case in usage, just trying to take a simple picture consistently
we are not talking about a feature issue where it doesn't quite work the way you want, it crashes the whole app hard!
we are not talking about a hard to recreate, only happening to a few people case - it seems from what I have read the Camera integration is fundamentally broken and I have spent days researching this and only found frustration from people out there
we are not talking about an issue that does not have consequences - in several places on this forum and others people have emphasized how it is affecting their platform decisions, ability to submit apps. You even have people on this board recommending that not to use Flex Mobile and move to other platforms. Not what you want to be happening to when you are at the adoption phase of a new product.
And that is the response - on this thread and here http://forums.adobe.com/message/4125590#4125590 - we know its an issue but we don't know when it will be fixed and no proactive communication on status - only a growing body of people like me getting increasingly frustrated. What does it take for an issue to be a show stopper? priority 1? affecting customer decisions priority?
In my case I am in place where I am trying to make a platform decision and since this experience has happened I have subscribed to the live feed for this forum and as many relevant Adoble blogs, news feed etc. as I could find. I did this to get a feel for how well Adobe is supporting the mobile development on the AIR platform. Something increasingly important given recent decisions.
My perception so far is quite poor especially for a recently released product, i.e. 4.6 release. In fact the release that finally addresses performance enough to make AIR mobile development a risk free decision. You would expect Adobe to be all over the boards like this - with core developers, platform experts contributing actively. My perception, rightly or wrongly, is of a community trying to support itself without much help, or clear communication from Adobe. In fact if you look at the the articles coming out of Adobe recently its all phonegap, html5 etc. It does not fill you with confidence for the future.
To be clear - I have had a great experience with actionscript, flex etc and as a company we have developed the backend portion of our platform solely on Flex. I don't believe that we could have done it any other way and even now when I look at the alternatives for web development I feel vindicated in our decision.
However, this rant is caused by a genuine frustration and fear. I don't expect this to get a meaningful response but maybe if there are enough voices it will create an overall improvement.
Sean

Doubt in memory allocation

Hi..
I have doubt in object memory allocation. for example see the following code,
String str = new String(JAVA PROGRAMMING);
1) int index = str.toLowerCase( ).indexOf("ram", 0);
2) String temp = str.toLowerCase( );
int index = temp.indexOf("ram", 0);
Ques:
from the above two form of coding which one is advicible and gives good performance.
what will happen when i execute str.toLowerCase( ).indexOf("ram", 0);, i mean wthether i will do the lowercase conversion in same memory location or create temporary memory area.

It means that the memory of a String is never reused to
hold for example a substring. The substring will
always be allocated in new memory. �Are you sure?
     * Initializes a newly created <code>String</code> object so that it
     * represents the same sequence of characters as the argument; in other
     * words, the newly created string is a copy of the argument string. Unless
     * an explicit copy of <code>original</code> is needed, use of this
     * constructor is unnecessary since Strings are immutable.
     * @param   original   a <code>String</code>.
    public String(String original) {
     this.count = original.count;
     if (original.value.length > this.count) {
         // The array representing the String is bigger than the new
         // String itself. Perhaps this constructor is being called
         // in order to trim the baggage, so make a copy of the array.
         this.value = new char[this.count];
         System.arraycopy(original.value, original.offset,
                    this.value, 0, this.count);
     } else {
         // The array representing the String is the same
         // size as the String, so no point in making a copy.
         this.value = original.value;
     }

Memory Alloc rises when dragging iPhone Simulator

Similar Messages

Maybe you are looking for