running out of memory

by shweta kumari » Tue, 03 Feb 2009 02:02:17 GMT


Sponsored Links
 Hi,

I am running a script that runs randomly the browser and music.After 7-8
instances of browser getting opened I see the following error :-

D/AndroidRuntime(  992): Shutting down VM
W/dalvikvm(  992): threadid=3: thread exiting with uncaught exception
(group=0x4000fe68)
E/AndroidRuntime(  992): Uncaught handler: thread main exiting due to
uncaught exception
E/AndroidRuntime(  992): java.lang.NullPointerException
E/AndroidRuntime(  992):   at
android.app.SearchDialog.jamSuggestionQuery(SearchDialog.java:921)
E/AndroidRuntime(  992):   at
android.app.SearchDialog.onItemSelected(SearchDialog.java:1451)
E/AndroidRuntime(  992):   at
android.widget.AdapterView.fireOnSelected(AdapterView.java:856)
E/AndroidRuntime(  992):   at
android.widget.AdapterView.access$200(AdapterView.java:41)
E/AndroidRuntime(  992):   at
android.widget.AdapterView$SelectionNotifier.run(AdapterView.java:827)
E/AndroidRuntime(  992):   at
android.os.Handler.handleCallback(Handler.java:587)
E/AndroidRuntime(  992):   at
android.os.Handler.dispatchMessage(Handler.java:92)
E/AndroidRuntime(  992):   at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime(  992):   at
android.app.ActivityThread.main(ActivityThread.java:3790)
E/AndroidRuntime(  992):   at java.lang.reflect.Method.invokeNative(Native
Method)
E/AndroidRuntime(  992):   at
java.lang.reflect.Method.invoke(Method.java:521)
E/AndroidRuntime(  992):   at
com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:745)
E/AndroidRuntime(  992):   at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:503)
E/AndroidRuntime(  992):   at dalvik.system.NativeStart.main(Native Method)
I/Process (  824): Sending signal. PID: 992 SIG: 3
I/dalvikvm(  992): threadid=7: reacting to signal 3
W/ActivityManager(  824): Force-killing crashed app com.android.browser at
watcher's request
I/Process (  824): Sending signal. PID: 992 SIG: 9
I/ActivityManager(  824): Process com.android.browser (pid 992) has died
I/WindowManager(  824): WIN DEATH: Window{43841140
com.android.browser/com.android.browser.BrowserActivity}
I/WindowManager(  824): WIN DEATH: Window{438589b0
Panel:com.android.browser/com.android.browser.BrowserActivity}
W/WindowManager(  824): No focus window, dropping: KeyEvent{action=1 code=21
repeat=0 meta=0 scancode=0 mFlags=0}
V/ActivityThread(  869): Resuming ActivityRecord{436cfbd0
token=android.os.binderpr...@436cf660{com.android.launcher/com.android.launcher.Launcher}}
with isForward=false
I/ActivityManager(  824): Low Memory: No more background processes.
D/dalvikvm(  891): GC freed 6207 objects / 226360 bytes in 267ms
D/dalvikvm(  824): GC freed 7734 objects / 346640 bytes in 354ms
I/AndroidRuntime(  983): AndroidRuntime onExit calling exit(4973)

Is it possible to open the browser windows consecutively for 10
mins.Secondly why does the background process get killed?

Thanks,
Shweta

--~--~---------~--~----~------------~-------~--~----~



running out of memory

by shweta kumari » Tue, 03 Feb 2009 16:53:05 GMT


 i All,

When i run the browser StartActivityLocked() is called which runs the
activity with some pid. If i open 4 browser windows on UI for each instance
the same process is called (as noted from pid).Does the memory get allocated
for each window? If this process goes
into background state and the foreground process needs memory how the memory
handler works?

Thanks,
Shweta

On Mon, Feb 2, 2009 at 11:21 AM, shweta kumari <shweta.n...@gmail.com>wrote:


--~--~---------~--~----~------------~-------~--~----~


Sponsored Links


Other Threads

1. Search Suggestions/Autocomplete OnClick Behavior

I do this:

ADD TO XML: android:id="@string/myACTV"

NOW CODE:

AutoCompleteTextView myTextView =
(AutoCompleteTextView)findViewById(R.id.myACTV);

myTextView.setOnItemClickListener(
                new OnItemClickListener()
                        {
                                public void onItemClick(AdapterView<?> parent, 
View view, int
position, long id)
                                {
                                        //your code here!
                                }
                        });








-- 

2. Periodic VerifyError on Android 1.5 related to GeoPoint in signature

As per javadocs, Verify error is "thrown when the 'verifier' detects
that a class file, though well formed, contains some sort of internal
inconsistency or security problem".
I encountered it once before when I was trying to instantiate
different classes by checking the version of sdk. Even though I
ensured that the right class will be instantiated depending on the
sdk, somehow the vm could see my 'else' part and it sometimes threw
the 'Verify Error'. Probably the fact that I am even trying to
instantiate a class which does not exist for the platform led to this
error. Solved the problem by seeing how the business card sample app
uses reflection.

In your case, it seems like GeoPoint class is not present on all
devices and so a Verify Error is being thrown (if not verified, an
exception will be thrown later when this class is instantiated). What
you can probably do is that use reflection to instantiate the above
class, and then handle the exception gracefully. Or you can check the
platform version and then instantiate the LocationHelper class (once
again using reflection).

Check out 
http://developer.android.com/resources/samples/BusinessCard/src/com/example/android/businesscard/ContactAccessor.html
for suggestions on how you can use reflection for platform dependent
stuff.




-- 

3. AnyBody to test My Application on Droid,N1.

4. Debugging on handset, can i send dummy gps cords?

5. how does two native shared library communicated?

6. Multiple overlay items

7. How to use OpenGL ES 1.x with android.view.View (without using GLSurfaceView) in Android 1.6?