Crashing

Hello. I have a relatively large form that crashes every so often with this showing up in the log. Once it crashes I can retry loading the form and it usually works.

Anyone seen this before?

Thanks,

Andrew

Hi Andrew,

What version of collect are you running and how big is the form? We
experienced the same problem with large forms running out of memory, the
problem should be fixed in the newer versions of collect. You should give
that a try.

Cheers,
Anton

··· On Tue, Jul 20, 2010 at 5:58 AM, Andrew Azman wrote:

Hello. I have a relatively large form that crashes every so often with
this http://dpaste.com/220045/ showing up in the log. Once it crashes I
can retry loading the form and it usually works.

Anyone seen this before?

Thanks,

Andrew

I am running v1.1.4. That is the newest release , right?

Thanks,

Andrew

··· On Jul 20, 2010, at 2:45 PM, Anton de Winter wrote:

Hi Andrew,

What version of collect are you running and how big is the form? We experienced the same problem with large forms running out of memory, the problem should be fixed in the newer versions of collect. You should give that a try.

Cheers,
Anton

On Tue, Jul 20, 2010 at 5:58 AM, Andrew Azman andrewazman@gmail.com wrote:
Hello. I have a relatively large form that crashes every so often with this showing up in the log. Once it crashes I can retry loading the form and it usually works.

Anyone seen this before?

Thanks,

Andrew

Just HOW big is your form?

Neil

··· On Tue, Jul 20, 2010 at 4:58 AM, Andrew Azman wrote:

Hello. I have a relatively large form that crashes every so often with
this http://dpaste.com/220045/ showing up in the log. Once it crashes I
can retry loading the form and it usually works.

Anyone seen this before?

Thanks,

Andrew

--
☞§※⌘:airplane::open_umbrella:
~Neil

sorry about the delay in this posting -- google groups thought it was
spam. v.1.1.4 is latest version. as far as form size, anton has a 400
instance form and neil's forms are about 500 instances.

··· On Tue, Jul 20, 2010 at 05:49, Andrew Azman wrote: > I am running v1.1.4. That is the newest release , right? > Thanks, > Andrew > On Jul 20, 2010, at 2:45 PM, Anton de Winter wrote: > > Hi Andrew, > What version of collect are you running and how big is the form? We > experienced the same problem with large forms running out of memory, the > problem should be fixed in the newer versions of collect. You should give > that a try. > Cheers, > Anton > > On Tue, Jul 20, 2010 at 5:58 AM, Andrew Azman wrote: >> >> Hello. I have a relatively large form that crashes every so often >> with this showing up in the log. Once it crashes I can retry loading the >> form and it usually works. >> Anyone seen this before? >> Thanks, >> Andrew > >

Ah, but I think having multiple languages is what really makes large forms
jump in size quickly (enough to start hitting memory issues, anyway).

··· On Fri, Jul 23, 2010 at 8:15 AM, Yaw Anokwa wrote:

sorry about the delay in this posting -- google groups thought it was
spam. v.1.1.4 is latest version. as far as form size, anton has a 400
instance form and neil's forms are about 500 instances.

On Tue, Jul 20, 2010 at 05:49, Andrew Azman andrewazman@gmail.com wrote:

I am running v1.1.4. That is the newest release , right?
Thanks,
Andrew
On Jul 20, 2010, at 2:45 PM, Anton de Winter wrote:

Hi Andrew,
What version of collect are you running and how big is the form? We
experienced the same problem with large forms running out of memory, the
problem should be fixed in the newer versions of collect. You should
give
that a try.
Cheers,
Anton

On Tue, Jul 20, 2010 at 5:58 AM, Andrew Azman andrewazman@gmail.com wrote:

Hello. I have a relatively large form that crashes every so often
with this showing up in the log. Once it crashes I can retry loading
the

form and it usually works.
Anyone seen this before?
Thanks,
Andrew

Definitely. For us, going from one language to two essentially doubled the
file size (granted that might not be the best metric but just throwing it
out there).

-Anton

··· On Fri, Jul 23, 2010 at 12:00 PM, Carl Hartung wrote:

Ah, but I think having multiple languages is what really makes large forms
jump in size quickly (enough to start hitting memory issues, anyway).

On Fri, Jul 23, 2010 at 8:15 AM, Yaw Anokwa yanokwa@gmail.com wrote:

sorry about the delay in this posting -- google groups thought it was
spam. v.1.1.4 is latest version. as far as form size, anton has a 400
instance form and neil's forms are about 500 instances.

On Tue, Jul 20, 2010 at 05:49, Andrew Azman andrewazman@gmail.com wrote:

I am running v1.1.4. That is the newest release , right?
Thanks,
Andrew
On Jul 20, 2010, at 2:45 PM, Anton de Winter wrote:

Hi Andrew,
What version of collect are you running and how big is the form? We
experienced the same problem with large forms running out of memory, the
problem should be fixed in the newer versions of collect. You should
give
that a try.
Cheers,
Anton

On Tue, Jul 20, 2010 at 5:58 AM, Andrew Azman andrewazman@gmail.com wrote:

Hello. I have a relatively large form that crashes every so often
with this showing up in the log. Once it crashes I can retry loading
the

form and it usually works.
Anyone seen this before?
Thanks,
Andrew

Languages are the key issue. In my forms, 3/4 of the code is itext.
Making Language specific forms is a workaround.
We are getting ahead of ourselves anyway, the size of the form is
not necessarily the cause of the crash. Crash is more likely caused by a
malformed reference. AA, have you run this through the validator? (some
things will still make it through validation and crash, but let's start
there.)

Next step is to isolate the bad code. Cut the form in half, run the first
half, see if it crashes. Run the second half, see if it crashes.
Select the crash side, split it and isolate the part of the code that
crashes. Lather, Rinse, Repeat. Iterate until you locate the line of code
that is harassing you. Don't forget that it may be more than one line of
code in more than one place, but isolating blocks of code that are 'good' is
the way to go.

N

··· On Fri, Jul 23, 2010 at 11:00 AM, Carl Hartung wrote:

Ah, but I think having multiple languages is what really makes large forms
jump in size quickly (enough to start hitting memory issues, anyway).

On Fri, Jul 23, 2010 at 8:15 AM, Yaw Anokwa yanokwa@gmail.com wrote:

sorry about the delay in this posting -- google groups thought it was
spam. v.1.1.4 is latest version. as far as form size, anton has a 400
instance form and neil's forms are about 500 instances.

On Tue, Jul 20, 2010 at 05:49, Andrew Azman andrewazman@gmail.com wrote:

I am running v1.1.4. That is the newest release , right?
Thanks,
Andrew
On Jul 20, 2010, at 2:45 PM, Anton de Winter wrote:

Hi Andrew,
What version of collect are you running and how big is the form? We
experienced the same problem with large forms running out of memory, the
problem should be fixed in the newer versions of collect. You should
give
that a try.
Cheers,
Anton

On Tue, Jul 20, 2010 at 5:58 AM, Andrew Azman andrewazman@gmail.com wrote:

Hello. I have a relatively large form that crashes every so often
with this showing up in the log. Once it crashes I can retry loading
the

form and it usually works.
Anyone seen this before?
Thanks,
Andrew

--
☞§※⌘:airplane::open_umbrella:
~Neil

Thanks for the responses. We have just over 500 data fields and so far have only one language. Another 3 languages will be added in the next week and I suspect we will start hitting some more issues. Luckily when it does crash it usually loads fine the next time.

Any tricks to optimize the memory management?

Thanks,
Andrew

··· On Jul 23, 2010, at 6:00 PM, Carl Hartung wrote:

Ah, but I think having multiple languages is what really makes large forms jump in size quickly (enough to start hitting memory issues, anyway).

On Fri, Jul 23, 2010 at 8:15 AM, Yaw Anokwa yanokwa@gmail.com wrote:
sorry about the delay in this posting -- google groups thought it was
spam. v.1.1.4 is latest version. as far as form size, anton has a 400
instance form and neil's forms are about 500 instances.

On Tue, Jul 20, 2010 at 05:49, Andrew Azman andrewazman@gmail.com wrote:

I am running v1.1.4. That is the newest release , right?
Thanks,
Andrew
On Jul 20, 2010, at 2:45 PM, Anton de Winter wrote:

Hi Andrew,
What version of collect are you running and how big is the form? We
experienced the same problem with large forms running out of memory, the
problem should be fixed in the newer versions of collect. You should give
that a try.
Cheers,
Anton

On Tue, Jul 20, 2010 at 5:58 AM, Andrew Azman andrewazman@gmail.com wrote:

Hello. I have a relatively large form that crashes every so often
with this showing up in the log. Once it crashes I can retry loading the
form and it usually works.
Anyone seen this before?
Thanks,
Andrew

Have we tried to interpret the stack trace?
I see that the form Ghana Safe Water Enterprise Survey
dumps a couple errors that look diagnostic:

( 1860): Uncaught handler: thread AsyncTask #4 exiting due to uncaught exception

and

( 1860): Caused by: java.lang.OutOfMemoryError

So, are we looking at a pure out-of-memory issue, or is the out-of-memory
being caused by an "uncaught exception" in the first place?

thoughts anyone?

··· On Sat, Jul 24, 2010 at 7:50 AM, Andrew Azman wrote:

Thanks for the responses. We have just over 500 data fields and so far
have only one language. Another 3 languages will be added in the next week
and I suspect we will start hitting some more issues. Luckily when it does
crash it usually loads fine the next time.

Any tricks to optimize the memory management?

Thanks,
Andrew

On Jul 23, 2010, at 6:00 PM, Carl Hartung wrote:

Ah, but I think having multiple languages is what really makes large forms
jump in size quickly (enough to start hitting memory issues, anyway).

On Fri, Jul 23, 2010 at 8:15 AM, Yaw Anokwa yanokwa@gmail.com wrote:

sorry about the delay in this posting -- google groups thought it was
spam. v.1.1.4 is latest version. as far as form size, anton has a 400
instance form and neil's forms are about 500 instances.

On Tue, Jul 20, 2010 at 05:49, Andrew Azman andrewazman@gmail.com wrote:

I am running v1.1.4. That is the newest release , right?
Thanks,
Andrew
On Jul 20, 2010, at 2:45 PM, Anton de Winter wrote:

Hi Andrew,
What version of collect are you running and how big is the form? We
experienced the same problem with large forms running out of memory, the
problem should be fixed in the newer versions of collect. You should
give
that a try.
Cheers,
Anton

On Tue, Jul 20, 2010 at 5:58 AM, Andrew Azman andrewazman@gmail.com wrote:

Hello. I have a relatively large form that crashes every so often
with this showing up in the log. Once it crashes I can retry loading
the

form and it usually works.
Anyone seen this before?
Thanks,
Andrew

--
☞§※⌘:airplane::open_umbrella:
~Neil

Neil,

Thanks for keeping this thread alive. The form has passed the validator. This form is still a work in progress and since this is not an error that occurs each and every time it is pretty difficult to isolate the bad code as suggested. We will be training surveyors next week and that should provide sufficient ODK time to see what is going on.

I will report back if this problem persists.

a

··· On Jul 23, 2010, at 8:26 PM, Neil Hendrick wrote:

Languages are the key issue. In my forms, 3/4 of the code is itext.
Making Language specific forms is a workaround.
We are getting ahead of ourselves anyway, the size of the form is not necessarily the cause of the crash. Crash is more likely caused by a malformed reference. AA, have you run this through the validator? (some things will still make it through validation and crash, but let's start there.)

Next step is to isolate the bad code. Cut the form in half, run the first half, see if it crashes. Run the second half, see if it crashes.
Select the crash side, split it and isolate the part of the code that crashes. Lather, Rinse, Repeat. Iterate until you locate the line of code that is harassing you. Don't forget that it may be more than one line of code in more than one place, but isolating blocks of code that are 'good' is the way to go.

N

On Fri, Jul 23, 2010 at 11:00 AM, Carl Hartung carlhartung@gmail.com wrote:
Ah, but I think having multiple languages is what really makes large forms jump in size quickly (enough to start hitting memory issues, anyway).

On Fri, Jul 23, 2010 at 8:15 AM, Yaw Anokwa yanokwa@gmail.com wrote:
sorry about the delay in this posting -- google groups thought it was
spam. v.1.1.4 is latest version. as far as form size, anton has a 400
instance form and neil's forms are about 500 instances.

On Tue, Jul 20, 2010 at 05:49, Andrew Azman andrewazman@gmail.com wrote:

I am running v1.1.4. That is the newest release , right?
Thanks,
Andrew
On Jul 20, 2010, at 2:45 PM, Anton de Winter wrote:

Hi Andrew,
What version of collect are you running and how big is the form? We
experienced the same problem with large forms running out of memory, the
problem should be fixed in the newer versions of collect. You should give
that a try.
Cheers,
Anton

On Tue, Jul 20, 2010 at 5:58 AM, Andrew Azman andrewazman@gmail.com wrote:

Hello. I have a relatively large form that crashes every so often
with this showing up in the log. Once it crashes I can retry loading the
form and it usually works.
Anyone seen this before?
Thanks,
Andrew

--
☞§※⌘:airplane::open_umbrella:
~Neil

Hey Andrew,
If you're using 1.1.4, you might try loading and closing your form several
times and see if on the 4-5th try is when the error shows up. There's a bug
in how android handles memory in background tasks which seems to have been
the problem before. That bug has been fixed in the latest trunk, and we're
trying to get the next release out soon.
-Carl

··· On Tue, Jul 27, 2010 at 8:26 AM, Andrew Azman wrote:

Neil,

Thanks for keeping this thread alive. The form has passed the validator.
This form is still a work in progress and since this is not an error that
occurs each and every time it is pretty difficult to isolate the bad code as
suggested. We will be training surveyors next week and that should provide
sufficient ODK time to see what is going on.

I will report back if this problem persists.

a

On Jul 23, 2010, at 8:26 PM, Neil Hendrick wrote:

Languages are the key issue. In my forms, 3/4 of the code is itext.
Making Language specific forms is a workaround.
We are getting ahead of ourselves anyway, the size of the form is
not necessarily the cause of the crash. Crash is more likely caused by a
malformed reference. AA, have you run this through the validator? (some
things will still make it through validation and crash, but let's start
there.)

Next step is to isolate the bad code. Cut the form in half, run the first
half, see if it crashes. Run the second half, see if it crashes.
Select the crash side, split it and isolate the part of the code that
crashes. Lather, Rinse, Repeat. Iterate until you locate the line of code
that is harassing you. Don't forget that it may be more than one line of
code in more than one place, but isolating blocks of code that are 'good' is
the way to go.

N

On Fri, Jul 23, 2010 at 11:00 AM, Carl Hartung carlhartung@gmail.comwrote:

Ah, but I think having multiple languages is what really makes large forms
jump in size quickly (enough to start hitting memory issues, anyway).

On Fri, Jul 23, 2010 at 8:15 AM, Yaw Anokwa yanokwa@gmail.com wrote:

sorry about the delay in this posting -- google groups thought it was
spam. v.1.1.4 is latest version. as far as form size, anton has a 400
instance form and neil's forms are about 500 instances.

On Tue, Jul 20, 2010 at 05:49, Andrew Azman andrewazman@gmail.com wrote:

I am running v1.1.4. That is the newest release , right?
Thanks,
Andrew
On Jul 20, 2010, at 2:45 PM, Anton de Winter wrote:

Hi Andrew,
What version of collect are you running and how big is the form? We
experienced the same problem with large forms running out of memory,
the
problem should be fixed in the newer versions of collect. You should
give
that a try.
Cheers,
Anton

On Tue, Jul 20, 2010 at 5:58 AM, Andrew Azman andrewazman@gmail.com wrote:

Hello. I have a relatively large form that crashes every so often
with this showing up in the log. Once it crashes I can retry loading
the

form and it usually works.
Anyone seen this before?
Thanks,
Andrew

--
☞§※⌘:airplane::open_umbrella:
~Neil