I'm hoping someone can help with this one, I see there are several others experiencing similar issues, but none of their solutions have worked. The app uses 2 plugins, the "Menu Buttons" and the "NAD Advanced Quiz". The problem is when "Refresh All Data" is used running the app in the emulator, 9 times out of 10 the app crashes with an Out Of Memory problem. Below is the LogCat from the last crash and the problem starts at the line I have separated out which reads "Out of memory on a 882682-byte allocation." I have tried everything I can find, but to no avail. This is being compiled as Android 4.0 with the Google Play Settings and being run in Android API14 emulator. Can anyone help please 05-11 11:14:23.223: W/ZZ(539): BT_device:updateDeviceSize This application considers this to be a "small device" 05-11 11:14:23.223: W/ZZ(539): BT_device:updateDeviceSize This device is in "portrait" orientation. 05-11 11:14:23.223: W/ZZ(539): BT_fragment_load_config_data:loadAppConfigData loading "BT_config.txt" from /assests folder in project... 05-11 11:14:23.993: W/ZZ(539): BT_fileManager: readTextFileFromAssets: "/BT_config.txt" 05-11 11:14:24.303: D/dalvikvm(539): GC_CONCURRENT freed 1400K, 20% free 13223K/16327K, paused 4ms+7ms 05-11 11:14:24.483: D/dalvikvm(539): GC_FOR_ALLOC freed 620K, 19% free 13388K/16327K, paused 78ms 05-11 11:14:24.483: I/dalvikvm-heap(539): Forcing collection of SoftReferences for 882682-byte allocation 05-11 11:14:24.613: D/dalvikvm(539): GC_BEFORE_OOM freed 0K, 19% free 13388K/16327K, paused 119ms 05-11 11:14:24.613: E/dalvikvm-heap(539): Out of memory on a 882682-byte allocation. 05-11 11:14:24.623: I/dalvikvm(539): "Thread-101" prio=5 tid=13 RUNNABLE 05-11 11:14:24.623: I/dalvikvm(539): | group="main" sCount=0 dsCount=0 obj=0x413d8d38 self=0x27c350 05-11 11:14:24.623: I/dalvikvm(539): | sysTid=583 nice=0 sched=0/0 cgrp=default handle=3115408 05-11 11:14:24.623: I/dalvikvm(539): | schedstat=( 805092101 429723661 124 ) utm=78 stm=2 core=0 05-11 11:14:24.623: I/dalvikvm(539): at java.lang.AbstractStringBuilder.enlargeBuffer(AbstractStringBuilder.java:~94) 05-11 11:14:24.623: I/dalvikvm(539): at java.lang.AbstractStringBuilder.append0(AbstractStringBuilder.java:145) 05-11 11:14:24.623: I/dalvikvm(539): at java.lang.StringBuilder.append(StringBuilder.java:216) 05-11 11:14:24.623: I/dalvikvm(539): at com.iospplexams.BT_fileManager.readTextFileFromAssets(BT_fileManager.java:371) 05-11 11:14:24.633: I/dalvikvm(539): at com.iospplexams.BT_fragment_load_config_data$3.run(BT_fragment_load_config_data.java:148) 05-11 11:14:24.633: W/dalvikvm(539): threadid=13: thread exiting with uncaught exception (group=0x409961f8) 05-11 11:14:24.653: E/AndroidRuntime(539): FATAL EXCEPTION: Thread-101 05-11 11:14:24.653: E/AndroidRuntime(539): java.lang.OutOfMemoryError 05-11 11:14:24.653: E/AndroidRuntime(539): at java.lang.AbstractStringBuilder.enlargeBuffer(AbstractStringBuilder.java:94) 05-11 11:14:24.653: E/AndroidRuntime(539): at java.lang.AbstractStringBuilder.append0(AbstractStringBuilder.java:145) 05-11 11:14:24.653: E/AndroidRuntime(539): at java.lang.StringBuilder.append(StringBuilder.java:216) 05-11 11:14:24.653: E/AndroidRuntime(539): at com.iospplexams.BT_fileManager.readTextFileFromAssets(BT_fileManager.java:371) 05-11 11:14:24.653: E/AndroidRuntime(539): at com.iospplexams.BT_fragment_load_config_data$3.run(BT_fragment_load_config_data.java:148) 05-11 11:14:24.684: W/ZZ(539): BT_activity_host:onPause 05-11 11:14:25.913: W/ZZ(539): iospplexams_appDelegate: onTrimMemory with level: 20 05-11 11:14:25.943: W/ZZ(539): BT_activity_host:onStop 05-11 11:14:25.943: W/ZZ(539): BT_screen_menuButtons:onDestroy JSON itemId: "7A2124B60F2F80A077F7FE2" itemType: "BT_screen_menuButtons" itemNickname: "Home_Menu" 05-11 11:14:25.943: W/ZZ(539): BT_screen_menuButtons:onDestroy JSON itemId: "433BA58AE7D7959E864C3E1" itemType: "BT_screen_menuButtons" itemNickname: "Aeroplanes_Menu" 05-11 11:14:25.943: W/ZZ(539): BT_activity_host:onDestroy 05-11 11:14:26.034: E/WindowManager(539): Activity com.iospplexams.BT_activity_host has leaked window com.android.internal.policy.impl.PhoneWindow$DecorView@411d2450 that was originally added here 05-11 11:14:26.034: E/WindowManager(539): android.view.WindowLeaked: Activity com.iospplexams.BT_activity_host has leaked window com.android.internal.policy.impl.PhoneWindow$DecorView@411d2450 that was originally added here 05-11 11:14:26.034: E/WindowManager(539): at android.view.ViewRootImpl.<init>(ViewRootImpl.java:343) 05-11 11:14:26.034: E/WindowManager(539): at android.view.WindowManagerImpl.addView(WindowManagerImpl.java:245) 05-11 11:14:26.034: E/WindowManager(539): at android.view.WindowManagerImpl.addView(WindowManagerImpl.java:193) 05-11 11:14:26.034: E/WindowManager(539): at android.view.WindowManagerImpl$CompatModeWrapper.addView(WindowManagerImpl.java:118) 05-11 11:14:26.034: E/WindowManager(539): at android.view.Window$LocalWindowManager.addView(Window.java:537) 05-11 11:14:26.034: E/WindowManager(539): at android.app.Dialog.show(Dialog.java:274) 05-11 11:14:26.034: E/WindowManager(539): at android.app.ProgressDialog.show(ProgressDialog.java:116) 05-11 11:14:26.034: E/WindowManager(539): at android.app.ProgressDialog.show(ProgressDialog.java:99) 05-11 11:14:26.034: E/WindowManager(539): at com.iospplexams.BT_fragment.showProgress(BT_fragment.java:306) 05-11 11:14:26.034: E/WindowManager(539): at com.iospplexams.BT_fragment_load_config_data.loadAppConfigDataAfterDelay(BT_fragment_load_config_data.java:102) 05-11 11:14:26.034: E/WindowManager(539): at com.iospplexams.BT_fragment_load_config_data.onCreateView(BT_fragment_load_config_data.java:88) 05-11 11:14:26.034: E/WindowManager(539): at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:795) 05-11 11:14:26.034: E/WindowManager(539): at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:998) 05-11 11:14:26.034: E/WindowManager(539): at android.app.BackStackRecord.run(BackStackRecord.java:622) 05-11 11:14:26.034: E/WindowManager(539): at android.app.FragmentManagerImpl.execPendingActions(FragmentManager.java:1330) 05-11 11:14:26.034: E/WindowManager(539): at android.app.FragmentManagerImpl$1.run(FragmentManager.java:417) 05-11 11:14:26.034: E/WindowManager(539): at android.os.Handler.handleCallback(Handler.java:605) 05-11 11:14:26.034: E/WindowManager(539): at android.os.Handler.dispatchMessage(Handler.java:92) 05-11 11:14:26.034: E/WindowManager(539): at android.os.Looper.loop(Looper.java:137) 05-11 11:14:26.034: E/WindowManager(539): at android.app.ActivityThread.main(ActivityThread.java:4340) 05-11 11:14:26.034: E/WindowManager(539): at java.lang.reflect.Method.invokeNative(Native Method) 05-11 11:14:26.034: E/WindowManager(539): at java.lang.reflect.Method.invoke(Method.java:511) 05-11 11:14:26.034: E/WindowManager(539): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:784) 05-11 11:14:26.034: E/WindowManager(539): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:551) 05-11 11:14:26.034: E/WindowManager(539): at dalvik.system.NativeStart.main(Native Method)

One thing you could try is to make sure all your images are in a png format. How many questions you have? LA

The total number of questions is in the region of 700.

Have you tried on a device? LA

I have not got a device to try it on at the moment, is it likely that the problem is confined to the emulator? Thanks for helping me with this.

I have not got a device to try it on at the moment, is it likely that the problem is confined to the emulator? Thanks for helping me with this.

Yes it could be but we need to rule a few things out. You can send me a link to it and I will try it for you on my device? LA

Here's the link: https://www.dropbox.com/s/cjwbm59wfc7pw6z/iospplexams.apk I do seem to be having a problem with one or 2 images causing crashes too, Question 10 of Aeroplanes>Flight Performance and Planning causes the crash as well as the refresh.

k will test in a few. LA

Works fine! There a specific screen you want me to test? LA

That's great news that it works OK. To be sure on the device it does not crash when you "refresh all data" either at the outset, or when you return to the home screen (with aeroplanes and helicopters as the choice) after starting one of the quizzes? I must update the links to the images in the online data to make it work properly after a refresh, so it will not be ready for a test after a refresh until Wednesday. Thank you so much for your help today, could I ask you to test it again on a specific screen next week? RM

This is one of the most frustrating things about Android. Different devices have different memory capacities, and there is no good rule of thumb. What's worse is that the memory you have access to is much smaller than the memory on the device. So you might have a nice, new Samsung phone with 8gb of memory and it doesn't help for jack, because your app only gets a few megabytes allocated to it. And different devices do it differently. Blah. Make sure your images are small, and use the hdpi, ldpi, mdli, etc folders. I've seen my apps crash over a single image that was about 250kb. I had to reduce the quality down to make the image less than 100kb. It sucks, but it's Android.

You can even try dragging the same images into all the folders. I usually see this crash on newer devices when the device tries to upscale the image, even if it doesn't need it.

Yeah, I tried refresh and the quizzes and I'm not getting a crash on my device. LA

Thank you LA for testing it, and for your comments Chris and Susan. I have copied the images into the other draw able folders, but it has not improved it on the emulator. Unfortunately one of the images needs to be reasonable quality to read its text, I guess I can only get around it by cropping it and putting different versions into the iOS and android devices. Thanks again.

Yes you have to have different images for IOS and Android. Which screen is it?

It is question 10 in the aeroplanes>Flight performance and planning. But it will only be question 10 if you have not refreshed the data after installing the apk. Otherwise it will have become a random selection from the question bank. It is the picture of Aberdeen asking about what hazard is near Loch Skeene. When you say I must have different images, I assume this is because of the size limit android can work with?

Yes Android has different sizes and should be in png format. Like chris1 said above. LA

Do the pixel dimensions have any effect on the crashes, or is it just the file size?

Dimensions do as well

The problem i have, is the other way round, my app crashes on a live device when refreshing , but not on the simulator, heres the log, anybody any ideas,the below is all in red. 06-27 09:06:29.179: E/AndroidRuntime(25824): FATAL EXCEPTION: Thread-3306 06-27 09:06:29.179: E/AndroidRuntime(25824): java.lang.OutOfMemoryError 06-27 09:06:29.179: E/AndroidRuntime(25824): at java.lang.AbstractStringBuilder.enlargeBuffer(AbstractStringBuilder.java:94) 06-27 09:06:29.179: E/AndroidRuntime(25824): at java.lang.AbstractStringBuilder.append0(AbstractStringBuilder.java:145) 06-27 09:06:29.179: E/AndroidRuntime(25824): at java.lang.StringBuilder.append(StringBuilder.java:216) 06-27 09:06:29.179: E/AndroidRuntime(25824): at com.uktheatres.BT_downloader.downloadTextData(BT_downloader.java:194) 06-27 09:06:29.179: E/AndroidRuntime(25824): at com.uktheatres.BT_fragment_load_config_data$3.run(BT_fragment_load_config_data.java:242) 06-27 09:06:29.279: W/ZZ(25824): BT_activity_host:onPause 06-27 09:06:30.639: W/ZZ(25824): uktheatres_appDelegate: onTrimMemory with level: 20 06-27 09:06:30.639: W/ZZ(25824): BT_activity_host:onStop 06-27 09:06:30.639: W/ZZ(25824): BT_activity_host:onDestroy 06-27 09:06:30.709: E/WindowManager(25824): Activity com.uktheatres.BT_activity_host has leaked window com.android.internal.policy.impl.PhoneWindow$DecorView{41445818 V.E..... R.....ID 0,0-580,162} that was originally added here 06-27 09:06:30.709: E/WindowManager(25824): android.view.WindowLeaked: Activity com.uktheatres.BT_activity_host has leaked window com.android.internal.policy.impl.PhoneWindow$DecorView{41445818 V.E..... R.....ID 0,0-580,162} that was originally added here 06-27 09:06:30.709: E/WindowManager(25824): at android.view.ViewRootImpl.<init>(ViewRootImpl.java:354) 06-27 09:06:30.709: E/WindowManager(25824): at android.view.WindowManagerGlobal.addView(WindowManagerGlobal.java:216) 06-27 09:06:30.709: E/WindowManager(25824): at android.view.WindowManagerImpl.addView(WindowManagerImpl.java:69) 06-27 09:06:30.709: E/WindowManager(25824): at android.app.Dialog.show(Dialog.java:281) 06-27 09:06:30.709: E/WindowManager(25824): at android.app.ProgressDialog.show(ProgressDialog.java:116) 06-27 09:06:30.709: E/WindowManager(25824): at android.app.ProgressDialog.show(ProgressDialog.java:99) 06-27 09:06:30.709: E/WindowManager(25824): at com.uktheatres.BT_fragment.showProgress(BT_fragment.java:306) 06-27 09:06:30.709: E/WindowManager(25824): at com.uktheatres.BT_fragment_load_config_data.loadAppConfigDataAfterDelay(BT_fragment_load_config_data.java:102) 06-27 09:06:30.709: E/WindowManager(25824): at com.uktheatres.BT_fragment_load_config_data.onCreateView(BT_fragment_load_config_data.java:88) 06-27 09:06:30.709: E/WindowManager(25824): at android.app.Fragment.performCreateView(Fragment.java:1695) 06-27 09:06:30.709: E/WindowManager(25824): at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:885) 06-27 09:06:30.709: E/WindowManager(25824): at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:1057) 06-27 09:06:30.709: E/WindowManager(25824): at android.app.BackStackRecord.run(BackStackRecord.java:682) 06-27 09:06:30.709: E/WindowManager(25824): at android.app.FragmentManagerImpl.execPendingActions(FragmentManager.java:1435) 06-27 09:06:30.709: E/WindowManager(25824): at android.app.FragmentManagerImpl$1.run(FragmentManager.java:441) 06-27 09:06:30.709: E/WindowManager(25824): at android.os.Handler.handleCallback(Handler.java:725) 06-27 09:06:30.709: E/WindowManager(25824): at android.os.Handler.dispatchMessage(Handler.java:92) 06-27 09:06:30.709: E/WindowManager(25824): at android.os.Looper.loop(Looper.java:137) 06-27 09:06:30.709: E/WindowManager(25824): at android.app.ActivityThread.main(ActivityThread.java:5227) 06-27 09:06:30.709: E/WindowManager(25824): at java.lang.reflect.Method.invokeNative(Native Method) 06-27 09:06:30.709: E/WindowManager(25824): at java.lang.reflect.Method.invoke(Method.java:511) 06-27 09:06:30.709: E/WindowManager(25824): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:795) 06-27 09:06:30.709: E/WindowManager(25824): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:562) 06-27 09:06:30.709: E/WindowManager(25824): at dalvik.system.NativeStart.main(Native Method)

ps followed all the directions above ie images in all drawable folders and all images under 100kb

In my case it was one image which was causing the problem. I suggest you remove all images and see if it works, then add the images one at a time to identify the problem image. Then gradually reduce the image file size until it works. I was also advised this is probably a problem with the emulator and might not occur on actual devices.

yeah mine is the other way around, works great on sim but crashes on real device, i have around 900 images, but i will try removing them and seeing if that works, cheers dude

nopr took every image out and still crashes, with the errors above, dont suppose you know what this error means do you android.view.WindowLeaked: Activity com.uktheatres.BT_activity_host has leaked window com.android.internal.policy.impl.PhoneWindow$DecorView{418ebdf0 V.E..... R.....ID 0,0-580,162} that was originally added here

Did you use all the drawable folders? I don't resize my images for all the folders unless I have problems, but I do drag them into the folders. Most of the plugins have set the images to "fit", so they will resize on the device. On one recent app I had to resize the home screen images to improve performance, but I generally don't resize them all. The up scaling on newer devices generally causes the crashes. If the high res drawable folder is empty, Eclipse assumes it needs to upscale the images on high res devices, and that is what causes the problem.

which folder is that susan, theres 5 and im presuming you mean the res folder

ive put all the header images in all the drawable folders, cleaned restarted ,refreshed and the header is still small susan, what am i doing wrong

That is a different problem. In the menu with image package, there is an extra folder and file you should drag into your project. It is the layout-sw600 folder. It is a layout specifically for tablets, and one of the things it does it resize the header image for tablets.

thats great thanks suze, will try that out, might fix few of my other probs, is there any way i can make the android project just use small settings as im thinking i will just release for phones till ive sorted out the large device probs, what its doing is using large settings on larger phones, which looks weird

where is the layout-sw600 folder susan :)

I think the setting is in the BT_devices class. There's a Boolean for isLargeDevice or something like that. It gets set if the width is over 500px. Change it to 5000 and you should be fine. (Or set it to false right after that)

The extra layout folder is in the plugin package. Download the package, unzip it, and drag that folder into your project under res.

@ chris o you mean here chris in the bt device java } //large or small device? if(this.deviceWidth > 600){ this.isLargeDevice = true; }else{ this.isLargeDevice = false; } i tried changing both 6000 and false separetly, saved, cleaned restarted, didnt do anything, am i in the place, @ susan cant find the folder, i downloaded the package with row icons plugin included, and i cant find it, do you mean download the plugin separately or as the complete package thanks sean

That should be it

tried your way chris didnt work, im probably doing something wrong, @ susan, found the plugin, downloaded the file, put the file in the res folder, i have, anim drawble drw hdpi drw ldpi draw mdpi draw xhdpi layout layout sw600dp values restarted, cleaned, removed app from emulator, restarted app , nothings changed, you know that im using the menu with image plugin and not menu rows dont you, what am i doing wrong susan thanks sean

You are close. Just drag the file, layout sw600dp in the project. The extra files in there resolve the header image and adjust the rows for tablet sizes. I would make Chris' change as well--that will not solve the problem with the header image in the tablet size, but if you have large and small header images it will make more sense for the high number of pixels in the current Android devices.

its not made any differance susan, i dragged the file into the res folder,restarted, cleaned and relaunched, images are still small, like the image i showed you, i presume i leave the files that are in the new folder, in the folder