Hi,
At times when my application is updated, then while update creates a new process for the application the old process also stays and does not die.
This results in a very confusing state for the app as both the processes are unaware of each other and they start to fight for resources.
Please note that we don't use "android : process" attribute anywhere in our app.
As an example consider this output of ps command from one of the devices which reached this state after the app update:
$ ps | grep my.app1
u0_a593 1224 471 944076 103284 ffffffff 00000000 S my.app1
u0_a593 23474 471 1051116 95848 ffffffff 00000000 S my.app1
Have faced this issue on variety of android devices including nexus 4 and nexus 5 running stock android.
At times when my application is updated, then while update creates a new process for the application the old process also stays and does not die.
This results in a very confusing state for the app as both the processes are unaware of each other and they start to fight for resources.
Please note that we don't use "android : process" attribute anywhere in our app.
As an example consider this output of ps command from one of the devices which reached this state after the app update:
$ ps | grep my.app1
u0_a593 1224 471 944076 103284 ffffffff 00000000 S my.app1
u0_a593 23474 471 1051116 95848 ffffffff 00000000 S my.app1
Have faced this issue on variety of android devices including nexus 4 and nexus 5 running stock android.