I don't have any process attributes in my manifest.xml... here it is:
?xml version=1.0 encoding=utf-8?
manifest xmlns:android=http://schemas.android.com/apk/res/android;
package=com.comp.duh.rm android:versionCode=1
android:versionName=@string/versionName
uses-sdk android:minSdkVersion=8
Thanks - I read that post; it seems to be stuck in the same place I am.
I suspect a memory leak that is keeping some app state alive across app
shutdown and restart, and what I'd really like is some easy way to analyze
what memory isn't being reclaimed when Android closes my app.
On
The onCreate of an Application (subclass) is called exactly *once *for each
instance of a DalvikVM.
If Android kills your app's process, it stops the DalvikVM instance as
well. There is no way to 'hold on' to any reference, since you DalvikVM
instance that was running your app no longer
Post your manifest.xml. I assume that you have your broadcastreceiver or
some service running in a separate process. That would cause
Application.onCreate to be called multiple times.
It would? Please provide a source for this piece of tidbit.
--
You received this message because you are
The onCreate.. method of the class extending Application is called only
once unless the process gets killed somehow and restarted. You can
investigate for any reason(s) of your process getting killed.
On Sunday, 11 November 2012 03:02:42 UTC+5:30, Craig wrote:
I received an error because I'm
My process getting killed should not be an issue, as long as it dies. I'm
scheduling alarms to start it up at different times - the issue I seem to
be having is that multiple instances of my process run at the same time...
On Sunday, November 11, 2012 3:27:30 AM UTC-5, Nitin Sethi wrote:
I think you should provide more details regarding what you're seeing that
makes you think the process is starting over again.
-
TreKing http://sites.google.com/site/rezmobileapps/treking - Chicago
Post your manifest.xml. I assume that you have your broadcastreceiver or
some service running in a separate process. That would cause
Application.onCreate to be called multiple times.
On Saturday, November 10, 2012 3:32:42 PM UTC-6, Craig wrote:
I received an error because I'm doing something
Here's my manifest.xml (with no process attributes):
?xml version=1.0 encoding=utf-8?
manifest xmlns:android=http://schemas.android.com/apk/res/android;
package=com.mypackage.rm android:versionCode=1
android:versionName=@string/versionName
uses-sdk android:minSdkVersion=8
On Mon, Nov 12, 2012 at 7:17 AM, Nobu Games dev.nobu.ga...@gmail.com wrote:
Post your manifest.xml. I assume that you have your broadcastreceiver or
some service running in a separate process. That would cause
Application.onCreate to be called multiple times.
ACRA keeps track of
Is there any remote service kind of thing is there?
Since i have observed this kind of behaviour in my application, in which i
used to create remote service.
On starting remote service, application onCreate method got executed.
I think it may helpful to u.
Regards,
Srihari babu.R
Hyderabad
--
On Tue, Jan 10, 2012 at 5:33 PM, srihari babu hisriharib...@gmail.com wrote:
Is there any remote service kind of thing is there?
Since i have observed this kind of behaviour in my application, in which i
used to create remote service.
On starting remote service, application onCreate method got
Instead of starting the service on onCreate(), you need to do the following
things.
1. start the service onPause.
2. check if service is not started.
--
Warm Regards,
*Mukesh Kumar*,
Android Consultant/Freelancer,
India,Hyderabad.
On Tue, Jan 10, 2012 at 2:03 PM, srihari babu
13 matches
Mail list logo
