search

rahul7386 / robotium

Automatically exported from code.google.com/p/robotium
0 stars 0 forks source link

Instrumentation run failed due to 'Process crashed.' #613

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
In my app, there is an Inbox in which i sent nearly 120 alert messages (format 
: pdf) and i downloaded them manually. I want to test whether my app opens all 
the 120 messages without any crash so that i can increase the number of 
messages. The problem is when it is opening 10 to 15 messages, iam getting 
following error 

Test run failed: Instrumentation run failed due to 'Process crashed.'

Expected output : I written the code in such a way that it should open all the 
inbox downloaded messages successfully. I want to see whether it opens all the 
messages with out any crash.

Robotium version : robotium 5.1 jar 
                   robotiumjavadoc 5.1 jar

Operating System : Windows 7

Original issue reported on code.google.com by af...@myedutor.com on 6 Jun 2014 at 10:50

GoogleCodeExporter commented 9 years ago 
Android Version : 4.0.3

Original comment by af...@myedutor.com on 6 Jun 2014 at 10:51

GoogleCodeExporter commented 9 years ago 
Can you please paste the log?

Original comment by renasr...@gmail.com on 8 Jun 2014 at 11:21

GoogleCodeExporter commented 9 years ago 
Hi,

Thanks for the reply... Please find the logcat as an attachment...

Original comment by af...@myedutor.com on 9 Jun 2014 at 12:44

GoogleCodeExporter commented 9 years ago 
There is no attachment.

Original comment by renasr...@gmail.com on 9 Jun 2014 at 12:45

GoogleCodeExporter commented 9 years ago 
Hi,
 please find the logcat below...

06-09 18:08:32.810: D/dalvikvm(2971): GC_CONCURRENT freed 744K, 24% free
6188K/8072K, paused 18ms+2ms, total 72ms
06-09 18:08:32.810: D/dalvikvm(2971): WAIT_FOR_CONCURRENT_GC blocked 23ms
06-09 18:08:32.900: D/dalvikvm(2971): GC_FOR_ALLOC freed 867K, 28% free
6675K/9172K, paused 30ms, total 30ms
06-09 18:08:33.140: D/dalvikvm(2971): GC_CONCURRENT freed 984K, 22% free
7741K/9852K, paused 3ms+4ms, total 61ms
06-09 18:08:33.140: D/dalvikvm(2971): WAIT_FOR_CONCURRENT_GC blocked 14ms
06-09 18:08:33.450: D/dalvikvm(2971): GC_CONCURRENT freed 888K, 19% free
8900K/10916K, paused 4ms+3ms, total 72ms
06-09 18:08:33.450: D/dalvikvm(2971): WAIT_FOR_CONCURRENT_GC blocked 31ms
06-09 18:08:33.610: W/System.err(2971): Connection lost (32109) -
java.io.EOFException
06-09 18:08:33.610: E/TVBService(1674): get_tvin_status error, device is
not open
06-09 18:08:33.630: W/System.err(2971): at
org.eclipse.paho.client.mqttv3.internal.CommsReceiver.run(CommsReceiver.java:119
)
06-09 18:08:33.630: W/System.err(2971): at
java.lang.Thread.run(Thread.java:856)
06-09 18:08:33.630: W/System.err(2971): Caused by: java.io.EOFException
06-09 18:08:33.630: W/System.err(2971): at
java.io.DataInputStream.readByte(DataInputStream.java:98)
06-09 18:08:33.630: W/System.err(2971): at
org.eclipse.paho.client.mqttv3.internal.wire.MqttInputStream.readMqttWireMessage
(MqttInputStream.java:51)
06-09 18:08:33.630: W/System.err(2971): at
org.eclipse.paho.client.mqttv3.internal.CommsReceiver.run(CommsReceiver.java:86)
06-09 18:08:33.630: W/System.err(2971): ... 1 more
06-09 18:08:33.630: E/MqttService(2971):  connection failed
06-09 18:08:33.630: E/MqttService(2971):  start reconnect
06-09 18:08:33.890: I/TVD_DEMO(3137): ERROR open /dev/video1 No such file
or directory
06-09 18:08:35.120: E/TVBService(1674): get_tvin_status error, device is
not open
06-09 18:08:36.620: E/TVBService(1674): get_tvin_status error, device is
not open
06-09 18:08:38.120: E/TVBService(1674): get_tvin_status error, device is
not open
06-09 18:08:38.920: I/TVD_DEMO(3142): ERROR open /dev/video1 No such file
or directory
06-09 18:08:39.610: E/TVBService(1674): get_tvin_status error, device is
not open
06-09 18:08:41.120: E/TVBService(1674): get_tvin_status error, device is
not open
06-09 18:08:42.620: E/TVBService(1674): get_tvin_status error, device is
not open
06-09 18:08:43.940: I/TVD_DEMO(3148): ERROR open /dev/video1 No such file
or directory
06-09 18:08:44.120: E/TVBService(1674): get_tvin_status error, device is
not open
06-09 18:08:45.620: E/TVBService(1674): get_tvin_status error, device is
not open
06-09 18:08:47.120: E/TVBService(1674): get_tvin_status error, device is
not open
06-09 18:08:48.620: E/TVBService(1674): get_tvin_status error, device is
not open
06-09 18:08:48.960: I/TVD_DEMO(3165): ERROR open /sys/devices/tvd/tvd No
such file or directory
06-09 18:08:48.960: I/TVD_DEMO(3165): ERROR open /dev/video1 No such file
or directory
06-09 18:08:50.110: E/TVBService(1674): get_tvin_status error, device is
not open
06-09 18:08:51.620: E/TVBService(1674): get_tvin_status error, device is
not open
06-09 18:08:53.120: E/TVBService(1674): get_tvin_status error, device is
not open
06-09 18:08:53.980: I/TVD_DEMO(3192): ERROR open /dev/video1 No such file
or directory
06-09 18:08:54.630: E/TVBService(1674): get_tvin_status error, device is
not open
06-09 18:08:56.130: E/TVBService(1674): get_tvin_status error, device is
not open
06-09 18:08:57.630: E/TVBService(1674): get_tvin_status error, device is
not open
06-09 18:08:59.010: I/TVD_DEMO(3209): ERROR open /sys/devices/tvd/tvd No
such file or directory
06-09 18:08:59.010: I/TVD_DEMO(3209): ERROR open /dev/video1 No such file
or directory
06-09 18:08:59.120: E/TVBService(1674): get_tvin_status error, device is
not open
06-09 18:09:00.630: E/TVBService(1674): get_tvin_status error, device is
not open
06-09 18:09:02.130: E/TVBService(1674): get_tvin_status error, device is
not open
06-09 18:09:02.980: E/MqttService(2971):  Received action of
MqttService.KEEPALIVE
06-09 18:09:02.980: E/MqttService(2971):  Keep alive
06-09 18:09:03.620: E/TVBService(1674): get_tvin_status error, device is
not open
06-09 18:09:03.630: E/MqttService(2971):  Received action of
MqttService.RECONNECT
06-09 18:09:03.630: E/MqttService(2971):  Action reconnect
06-09 18:09:03.630: E/MqttService(2971):  Connecting with URL: tcp://
173.255.254.228:3333
06-09 18:09:03.640: E/MqttService(2971):  Connecting with DataStore
06-09 18:09:04.030: I/TVD_DEMO(3227): ERROR open /sys/devices/tvd/tvd No
such file or directory
06-09 18:09:04.030: I/TVD_DEMO(3227): ERROR open /dev/video1 No such file
or directory
06-09 18:09:04.170: W/System.err(2971): Connection lost (32109) -
java.io.EOFException
06-09 18:09:04.170: W/System.err(2971): at
org.eclipse.paho.client.mqttv3.internal.CommsReceiver.run(CommsReceiver.java:119
)
06-09 18:09:04.170: W/System.err(2971): at
java.lang.Thread.run(Thread.java:856)
06-09 18:09:04.170: W/System.err(2971): Caused by: java.io.EOFException
06-09 18:09:04.180: W/System.err(2971): at
java.io.DataInputStream.readByte(DataInputStream.java:98)
06-09 18:09:04.180: W/System.err(2971): at
org.eclipse.paho.client.mqttv3.internal.wire.MqttInputStream.readMqttWireMessage
(MqttInputStream.java:51)
06-09 18:09:04.180: W/System.err(2971): at
org.eclipse.paho.client.mqttv3.internal.CommsReceiver.run(CommsReceiver.java:86)
06-09 18:09:04.180: W/System.err(2971): ... 1 more
06-09 18:09:04.180: E/MqttService(2971):  connection failed
06-09 18:09:04.180: E/MqttService(2971):  start reconnect
06-09 18:09:05.120: E/TVBService(1674): get_tvin_status error, device is
not open
06-09 18:09:06.630: E/TVBService(1674): get_tvin_status error, device is
not open

Original comment by af...@myedutor.com on 9 Jun 2014 at 12:47

GoogleCodeExporter commented 9 years ago 
The only thing I can see here is connection problem from the AUT. Nothing here 
points to Robotium causing this.

Original comment by renasr...@gmail.com on 9 Jun 2014 at 12:51

GoogleCodeExporter commented 9 years ago 
Hi,

I want to ask a general question. Are there any issues by using Robotium
 which leads to "Instrumentation test case failed due to Process crashed".

Scenario : I have written small code which performs clicking on view button
and waits for sometime and comes back repeatedly. After performing average
50 clicks iam getting the above error.

Original comment by af...@myedutor.com on 9 Jun 2014 at 1:01

GoogleCodeExporter commented 9 years ago 
No, we have not heard about an issue like that. I think the issue is with the 
AUT. Maybe its leaking memory or similar.

Original comment by renasr...@gmail.com on 9 Jun 2014 at 1:05