Database Users

Malloc/new never returns

I have a problem.
I make use of malloc or new in many places to store data in. I normally have no problem but there seems to be a limit on how much I can use it. I always free/delete as soon as I no longer need the memory and always check for 0 returned. I have mechanisms in place in case of 0 but when malloc actually fails it dose not return. Malloc just never returns and hence crashes my program. What could be the cause of this?
+The actual memory I am requesting is ~2-20k, the available memory is 20-30mb.
I am considering creating a heap, using it to allocate blocks from and destroying it to clean the memory. This is a time consuming change, dose anybody have some experience with this problem?
The annoying part is that the code works 100% on old devices and fails on new ones. I never thought i would be rewriting this code.

The heap way did work. The problem is that on ce, to create a heap you have to set aside the size first. Also there are still some problems I am having with memory that I pass out of a dll and then pass back in to free. Still its better than crashing! I may solve the freeing of individual pointers by just replacing it with a periodic call to HeapDestroy to clear them all out, something else that can't be done with malloc.

dalvik GC

hi -
is it possible to change the GC schedule to run when the phone is idle or when the CPU is below a certain threshold. Currently when ever the GC runs it runs when the user app needs memory, thus contributing to the need. trying to check if any one has changed the dalvik GC scheduler ?

GC does not do anything extensive.
All it does is to mark certain memory locations as free in the global memory table. This hardly contributes to any processing overhead and thus, there is no need for it to try and clean up after intervals.
Trying to do anything like that would be over-optimization and would lead to degraded performance and battery life.

Sims 3 install error "Couldn't clear application caches"

I didn't want to hijack the other Sims 3 heap thread although it may be related, so I'm asking here. The other thread made me think of the game and I thought I would give it a shot. When I start it, I suppose it needs to install, but it comes up and says out of space. I have 1.46gb available application storage, 125mb free memory and lot's of sdcard and sd storage.
Logcat says it couldn't clear application caches. Does anyone know why that would be?
Code:
I/ActivityManager( 2253): Starting activity: Intent { act=android.intent.action.
MAIN cat=[android.intent.category.LAUNCHER] flg=0x10000000 cmp=com.ea.sims3.laun
cher/.MainActivity }
W/Resources( 2253): Converting to boolean: TypedValue{t=0x3/d=0x16e8 "res/anim/a
ccelerate_decelerate_interpolator.xml" a=1 r=0x10a0004}
W/Resources( 2253): Converting to boolean: TypedValue{t=0x3/d=0x16e8 "res/anim/a
ccelerate_decelerate_interpolator.xml" a=1 r=0x10a0004}
W/Resources( 2253): Converting to boolean: TypedValue{t=0x3/d=0x16e8 "res/anim/a
ccelerate_decelerate_interpolator.xml" a=1 r=0x10a0004}
I/ActivityManager( 2253): Starting activity: Intent { act=android.intent.action.
VIEW dat=file:///data_tmo/games/ea/The%20Sims%203.apk typ=application/vnd.androi
d.package-archive cmp=com.android.packageinstaller/.PackageInstallerActivity }
W/Resources( 2253): Converting to boolean: TypedValue{t=0x3/d=0x16e8 "res/anim/a
ccelerate_decelerate_interpolator.xml" a=1 r=0x10a0004}
I/installd( 2213): free_cache(305247264) avail 72699904
W/PackageManager( 2253): Couldn't clear application caches
I/ActivityManager( 2253): Displayed activity com.android.packageinstaller/.Packa
geInstallerActivity: 140 ms (total 289 ms)

I'm having the same problem

yup same here in the midst of playing the game that pops up and kicks me out...

A clue, my dear Watson...
afive720 said:
I guess SIMS stores its data in the app partition which you are essentially relocating with this hack to a place where you have 130mb limit for your applications. This hack relies on apps to store their data somewhere else, like on SD card. Look at MODACO thread, some people were having issues with Google Maps even because apparently it caches stuff on apps partition. Anyways, I didn't feel much of a difference at all with the hack and without, I reverted and will keep it stock for now.
Click to expand...
Click to collapse
This makes sense... Have you all done the hack? I'll revert back and see what happens... Man, I'll miss the extra speed if this pans out to be the culprit...

Yepper, that was it. I reverted the data directory back to the original location, rebooted and The Sims 3 is now installing as I type... I guess that's good and bad news... I'll have to see how much the lagging annoys me and see which way I want to go... Anyways, hope this helps.

Mind telling how you fixed that error again step by step or where to find?

How I got my sims to work
First thing I had to do was uninstall the lag fix, as it would crash all the time as it was taking up to much of the memory. When back to normal non lag fix I would get the heap error when buying and moving stuff, usually could buy 2 things, or move 2 things, or one of each and then on the 3rd thing i would get the heap error. So following the suggestion of someone else that uprooted the entire garden and the error stopped, so i tried this and it fixed the heap error issue, I only tested for one day, but i moved and sold about 50 things in a row without an issue. Like i said before i could never even do 3 in a row. So no lag fix and not garden and everything works fine on the sims 3.
Credit goes to to lund0529 for figuring this out.

If your Roms have random 100% CPU peak problem.

If you 're using your perfect rom for a week and start notice cpu ramdomly become 100%.
check you alogcat if where are infinity GC then your dalvin memomry default as 24M might not enough. I have this problem and extend to 48M to eliminate it.

could you please put this in "noob" speak so I can do it. How do I extend it? This is the exact problem i am having and it is driving me nuts. Thanks you in advance.

alogcat is a program to watch log files (I guess it's available through Android's Market)
After installing that program you should check if you have lot of GC (Garbage Collector) entries in the logs. If you do, you need to raise your "dalvin memory" to 48M.
I'm still trying to figure out what "dalvin memory" means
Maybe he's talking about android's internal taskkiller: http://forum.xda-developers.com/showthread.php?t=622666
But that's a guess. Maybe someone can throw a light into this thread.

thank you my friend. i downloaded the app. i ran it and then my eyes glazed over. I can't tell if the "dalvin" is 24, 12 or 60. I, like you, just need to know what app/program i need to change the number up (if neccessary). thanks. hopefully others to weigh in. i am sick of switching builds. this one is perfect - outside of this glitch.

you can change the value with root explorer. You have to find the build.prop in the /system directory. in it there is :"
# This is a high density device with more memory, so larger vm heaps for it.
dalvik.vm.heapsize=24m
just change it to:
dalvik.vm.heapsize=32m or 48m
i hope it will help.

cpt_crabs said:
you can change the value with root explorer. You have to find the build.prop in the /system directory. in it there is :"
# This is a high density device with more memory, so larger vm heaps for it.
dalvik.vm.heapsize=24m
just change it to:
dalvik.vm.heapsize=32m or 48m
i hope it will help.
Click to expand...
Click to collapse
ok, so i looked in the android folder. I don't have a system folder at all. I have data, android apps, cache, media and root folders. I did a search using SUFBS and it did not pull up "build", "dalvik" or "prop". Any idea where I might find it or is there something I have to do more with the root explorer?

steve austin said:
ok, so i looked in the android folder. I don't have a system folder at all. I have data, android apps, cache, media and root folders. I did a search using SUFBS and it did not pull up "build", "dalvik" or "prop". Any idea where I might find it or is there something I have to do more with the root explorer?
Click to expand...
Click to collapse
Use root explorer.

i did. no luck.

steve austin said:
ok, so i looked in the android folder. I don't have a system folder at all. I have data, android apps, cache, media and root folders. I did a search using SUFBS and it did not pull up "build", "dalvik" or "prop". Any idea where I might find it or is there something I have to do more with the root explorer?
Click to expand...
Click to collapse
That's your problem. System is NOT in the android folder. it's higher up. Click on the two period at the top to get back to the top. You will see it.

steve austin said:
i did. no luck.
Click to expand...
Click to collapse
My apologies, I read your post wrong.
Make sure that in root explorer, you go to the actual root of the file system. Basically go "up" until you can't anymore. It's not in the "sdcard" directory.

This does not really solve anything.
It just makes all your apps take more memory...
With a larger heap and more objects the GC will most likely take 2x longer to run.
Total running time will be the same on prolonged usage.
TL;DR:
Don't do this.

Does the new App2SD update move the entire apps data?

Is it just me, or does it under App info on an app move the "Application" bytes and not the total bytes? If so this feature is completely useless because the "Application" part of the bytes is minute compared to the total. Completely defeats the purpose of the feature.

SlayaDud said:
Is it just me, or does it under App info on an app move the "Application" bytes and not the total bytes? If so this feature is completely useless because the "Application" part of the bytes is minute compared to the total. Completely defeats the purpose of the feature.
Click to expand...
Click to collapse
I think this is application dependent because a lot of games (at least from what I can see), the application portion is actually a majority. It doesn't move all it, but most of it. It seems like it usually leaves around 2MB on the phone itself and the rest gets moved to the SD card.