Re: [android-developers] Re: Android 2.3 Causes memory intensive app to crash
Any news on this? Have you had a chance to look into the app? I've currently put my current project on hold because this has made it impossible to develop for, so any feedback would be appreciated. Thanks! -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
Re: [android-developers] Re: Android 2.3 Causes memory intensive app to crash
Follow up to my OT reply. It seems like I'm not the only one experiencing the no more pmem available error since updating to 2.3.3. Happens even when using only built-in applications (with market updates). http://code.google.com/p/android/issues/detail?id=15135 -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Android 2.3 Causes memory intensive app to crash
Actually Zsolt i think the green icons is a feature that you should also see in the simulator - from the 2.3 manualhttp://www.google.nl/url?sa=tsource=webcd=2sqi=2ved=0CCsQFjABurl=http%3A%2F%2Fwww.google.com%2Fgooglephone%2FAndroidUsersGuide-2.3.pdfrct=jq=nexus%20s%20manualei=jJV0Tf-5GsqfOq7t5F0usg=AFQjCNGiUuQnTKXnryY1RGF8_2H-uGWAGQsig2=mqOD6AtYl6MM8QByXTM56A : Network status icons turn green if you have a Google Account added to your phone and the phone is connected to Google services I've also noticed that when turning my 3G on and off - like i constantly need to do on 2.3.3 to conserve battery - it stays white for a bit before it connects to the Google Services. -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Android 2.3 Causes memory intensive app to crash
Ah, thanks. That's a relief. On Mar 7, 4:25 pm, David Goemans dgoem...@gmail.com wrote: Actually Zsolt i think the green icons is a feature that you should also see in the simulator - from the 2.3 manualhttp://www.google.nl/url?sa=tsource=webcd=2sqi=2ved=0CCsQFjABurl... : Network status icons turn green if you have a Google Account added to your phone and the phone is connected to Google services I've also noticed that when turning my 3G on and off - like i constantly need to do on 2.3.3 to conserve battery - it stays white for a bit before it connects to the Google Services. -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Android 2.3 Causes memory intensive app to crash
Yeah, there's something really weird here. I know what Dianne is saying, but it shouldn't be my problem as an app developer if the phone can't handle other people's running apps. My simple test case this: I have a relative layout with an imageview as the fullscreen background and a button over it. I have an activity witch loads an image from the filesystem and assigns it to the image view This crashes with the above error. The OS, if anything, should kill background apps with fullscreen rendering and not my app. I discovered this problem while trying to write an image cropper intent for a live wallpaper ( since like Dianne has pointed out several times, the built in one is private API and should not be used ). The thing is the moment my image cropper loads, it bombs straight out with this error. Gingerbread on my Nexus One has actually been relatively unstable, with the homescreen and many other apps i normally use crashing several times, and i think it's this error going on. -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
Re: [android-developers] Re: Android 2.3 Causes memory intensive app to crash
Could you please send me your app with steps to reproduce? On Sun, Mar 6, 2011 at 9:07 AM, dgoemans dgoem...@gmail.com wrote: Yeah, there's something really weird here. I know what Dianne is saying, but it shouldn't be my problem as an app developer if the phone can't handle other people's running apps. My simple test case this: I have a relative layout with an imageview as the fullscreen background and a button over it. I have an activity witch loads an image from the filesystem and assigns it to the image view This crashes with the above error. The OS, if anything, should kill background apps with fullscreen rendering and not my app. I discovered this problem while trying to write an image cropper intent for a live wallpaper ( since like Dianne has pointed out several times, the built in one is private API and should not be used ). The thing is the moment my image cropper loads, it bombs straight out with this error. Gingerbread on my Nexus One has actually been relatively unstable, with the homescreen and many other apps i normally use crashing several times, and i think it's this error going on. -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -- Dianne Hackborn Android framework engineer hack...@android.com Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
Re: [android-developers] Re: Android 2.3 Causes memory intensive app to crash
Sure, i've just trimmed it down to a single activity and 1 image being loaded ( this time not directly from the file system, but rather specified in the XML ). It loads a bit better, but still crashes: Here's the source: http://dgoemans.com/Storage/ImageCrash.zip 1. Run the app 2. Image shows, hit the back button on the phone 3. Repeat Eventually i see in the debug output on hitting back that crash. After a few tries of that my homescreen crashed. After the homescreen crashed ( had to hit home to get it to force loading ), the app wouldn't load the image anymore and the above mentioned crash occured everytime on launching my app. All launches were done with the debugger attached, and my hardware is a Nexus One ( the one received from Google - thanks!! - for the device seeding program last year ). In the more advanced case - my actual app. I'm launching an intent from the wallpaper settings dialog. This crashes immediately, i assume because the Surface memory taken by the wallpaper rendering in the background pushes everything over the limit? On a side note, my confirm function - sending a bitmap through a bundle - should work right? I understand if you choose not to respond to that :) Finally, Thanks for responding on a Sunday, another reason i have an insane amount of respect for the Android team!! David Goemans -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
Re: [android-developers] Re: Android 2.3 Causes memory intensive app to crash
Just use gmaps and other built in apps. That is enough to cause intermittent drawing issues because of no more pmem available in the default launcher when pressing home on my nexus one with 2.3.3. Factory reset does not help. -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
Re: [android-developers] Re: Android 2.3 Causes memory intensive app to crash
ye, just after sending the previous message i wanted to take a photo of what's turning out to be a beautiful sunset, and the camera and gallery app crashed several times, eventually the homescreen too. -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
Re: [android-developers] Re: Android 2.3 Causes memory intensive app to crash
That's very strange? Which device is this on? I have been using 2.3.3 extensively for months and months without seeing such issues... I also have been using it on N1 for many months, but I don't use my N1 as much these days. Anyway, I'll take a look at the app. On Sun, Mar 6, 2011 at 9:48 AM, David Goemans dgoem...@gmail.com wrote: ye, just after sending the previous message i wanted to take a photo of what's turning out to be a beautiful sunset, and the camera and gallery app crashed several times, eventually the homescreen too. -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -- Dianne Hackborn Android framework engineer hack...@android.com Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
Re: [android-developers] Re: Android 2.3 Causes memory intensive app to crash
N1 running 2.3.3. But i noticed some bug threads about the deployed version of 2.3.3 to the N1, both this issue and the battery life issue, so there's a good chance that what was deployed to the public had some extra issues that you didn't see on the internal builds. Alternatively these issues may be related to external apps that don't work well with 2.3.3. -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Android 2.3 Causes memory intensive app to crash
The 2.3.3 image on N1 is definetely not the same as the SDK image running on the emulator. The one visible difference I noticed is that some of the toolbar icons (3G, signal strength) are green on the N1, while they are white on the SDK. Since these icons are defined at the high level Java layer, who knows what else can be different. On Mar 7, 4:21 am, David Goemans dgoem...@gmail.com wrote: N1 running 2.3.3. But i noticed some bug threads about the deployed version of 2.3.3 to the N1, both this issue and the battery life issue, so there's a good chance that what was deployed to the public had some extra issues that you didn't see on the internal builds. Alternatively these issues may be related to external apps that don't work well with 2.3.3. -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Android 2.3 Causes memory intensive app to crash
I've also noticed this, it might be an app causing it. But it makes the system go into an unstable state. I've had google maps and the launcher effectivly stop working. -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Android 2.3 Causes memory intensive app to crash
Ow and something important: i stopped my app, but now the whole system becomes instable, screens do not show anymore.. i logcatted it.. and look at it below. It looks like my app made the whole system unstable. I am going to reboot my phone now... 03-04 00:04:51.468: DEBUG/GraphicBufferAllocator(96): 0x54a788: 1500.00 KiB | 480 ( 480) x 800 |2 | 0x0133 03-04 00:04:51.468: DEBUG/GraphicBufferAllocator(96): 0x54ebb0: 746.25 KiB | 480 ( 480) x 398 |1 | 0x0133 03-04 00:04:51.468: DEBUG/GraphicBufferAllocator(96): 0x5809e8: 157.50 KiB | 480 ( 480) x 84 |1 | 0x0133 03-04 00:04:51.468: DEBUG/GraphicBufferAllocator(96): 0x585000: 1500.00 KiB | 480 ( 480) 03-04 00:04:51.468: ERROR/SurfaceFlinger(96): Layer::requestBuffer(this=0x488ed0), index=0, w=800, h=718 failed (Out of memory) 03-04 00:04:51.468: ERROR/Surface(155): Surface (identity=4) requestBuffer(0, 0, 0, 0, 0033) returned a buffer with a null handle 03-04 00:04:51.468: ERROR/Surface(155): getBufferLocked(0, 0, 0, 0, 0033) failed (Out of memory) 03-04 00:04:51.468: ERROR/Surface(155): dequeueBuffer failed (Out of memory) 03-04 00:04:51.498: ERROR/qsd8k.gralloc(96): /dev/pmem: no more pmem available 03-04 00:04:51.498: ERROR/qsd8k.gralloc(96): couldn't open pmem (Unknown error: 0) 03-04 00:04:51.498: ERROR/qsd8k.gralloc(96): gralloc failed err=Out of memory 03-04 00:04:51.498: WARN/GraphicBufferAllocator(96): alloc(800, 442, 1, 0133, ...) failed -12 (Out of memory) 03-04 00:04:51.498: DEBUG/GraphicBufferAllocator(96): Allocated buffers: 03-04 00:04:51.498: DEBUG/GraphicBufferAllocator(96): 0x40f358: 723.75 KiB | 480 ( 480) x 386 |1 | 0x0133 03-04 00:04:51.498: DEBUG/GraphicBufferAllocator(96): 0x435788: 750.00 KiB | 480 ( 480) x 800 |4 | 0x0133 03-04 00:04:51.498: DEBUG/GraphicBufferAllocator(96): 0x47d640: 723.75 KiB | 480 ( 480) x 386 |1 | 0x0133 03-04 00:04:51.498: DEBUG/GraphicBufferAllocator(96): 0x483160: 1018.75 KiB | 800 ( 800) x 326 |1 | 0x0133 03-04 00:04:51.498: DEBUG/GraphicBufferAllocator(96): 0x4afd50: 1500.00 KiB | 480 ( 480) x 800 |2 | 0x0133 03-04 00:04:51.498: DEBUG/GraphicBufferAllocator(96): 0x4e0060: 1500.00 KiB | 480 ( 480) x 800 |2 | 0x0133 03-04 00:04:51.498: DEBUG/GraphicBufferAllocator(96): 0x504da0: 448.00 KiB | 432 ( 448) x 256 |1 | 0x0133 03-04 00:04:51.498: DEBUG/GraphicBufferAllocator(96): 0x506738: 1428.75 KiB | 480 ( 480) x 762 |2 | 0x0133 03-04 00:04:51.498: DEBUG/GraphicBufferAllocator(96): 0x50fd30: 1500.00 KiB | 480 ( 480) x 800 |2 | 0x0133 03-04 00:04:51.498: DEBUG/GraphicBufferAllocator(96): 0x52cb18: 1018.75 KiB | 800 ( 800) x 326 |1 | 0x0133 03-04 00:04:51.498: DEBUG/GraphicBufferAllocator(96): 0x5451f0: 1500.00 KiB | 480 ( 480) x 800 |2 | 0x0133 03-04 00:04:51.498: DEBUG/GraphicBufferAllocator(96): 0x54a788: 1500.00 KiB | 480 ( 480) x 800 |2 | 0x0133 03-04 00:04:51.498: DEBUG/GraphicBufferAllocator(96): 0x54ebb0: 746.25 KiB | 480 ( 480) x 398 |1 | 0x0133 03-04 00:04:51.498: DEBUG/GraphicBufferAllocator(96): 0x5809e8: 157.50 KiB | 480 ( 480) x 84 |1 | 0x0133 03-04 00:04:51.498: DEBUG/GraphicBufferAllocator(96): 0x585000: 1500.00 KiB | 480 ( 480) 03-04 00:04:51.498: ERROR/SurfaceFlinger(96): Layer::requestBuffer(this=0x51e278), index=0, w=800, h=442 failed (Out of memory) 03-04 00:04:51.498: ERROR/Surface(96): Surface (identity=2589) requestBuffer(0, 0, 0, 0, 0033) returned a buffer with a null handle 03-04 00:04:51.498: ERROR/Surface(96): getBufferLocked(0, 0, 0, 0, 0033) failed (Out of memory) 03-04 00:04:51.498: ERROR/Surface(96): dequeueBuffer failed (Out of memory) 03-04 00:04:51.498: ERROR/ViewRoot(96): OutOfResourcesException locking surface 03-04 00:04:51.498: ERROR/ViewRoot(96): android.view.Surface $OutOfResourcesException 03-04 00:04:51.498: ERROR/ViewRoot(96): at android.view.Surface.lockCanvasNative(Native Method) 03-04 00:04:51.498: ERROR/ViewRoot(96): at android.view.Surface.lockCanvas(Surface.java:314) 03-04 00:04:51.498: ERROR/ViewRoot(96): at android.view.ViewRoot.draw(ViewRoot.java:1456) 03-04 00:04:51.498: ERROR/ViewRoot(96): at android.view.ViewRoot.performTraversals(ViewRoot.java:1258) 03-04 00:04:51.498: ERROR/ViewRoot(96): at android.view.ViewRoot.handleMessage(ViewRoot.java:1859) 03-04 00:04:51.498: ERROR/ViewRoot(96): at android.os.Handler.dispatchMessage(Handler.java:99) 03-04 00:04:51.498: ERROR/ViewRoot(96): at android.os.Looper.loop(Looper.java:123) 03-04 00:04:51.498: ERROR/ViewRoot(96): at com.android.server.WindowManagerService $PolicyThread.run(WindowManagerService.java:595) 03-04 00:04:51.498: ERROR/ViewRoot(155): OutOfResourcesException locking surface 03-04 00:04:51.498: ERROR/ViewRoot(155): android.view.Surface $OutOfResourcesException 03-04
