Android Question XML String Replace Problem

[SinanTasgin]

Hi ,

I have an issue about web services which i require your assistance. The device is working properly when i create an xmlString which has between 300-500 records in it.

But when it gets over 500 records (eg 1400) I replace my xmlString with a for loop. But unfotunately this makes the device pause and it terminates. I have the same issue when I run the program in debug mode and also in release mode.

The program runs the for loop for max 500 records but it terminates itself when records gets over 500. So I will be so grateful if you come up with an advice and help me out with this problem.

 

[DonManfred]

see the log for errors. There MUST be some who tells what´s wrong if the app just quits...

 

[SinanTasgin]

I can't see in log .

For loop is not finished .
Cursor2.RowCount = 1008
The sayac (counter ) is between 400 to 500 on average .
XML string for the overload hangs.
The loop should continue, however, the program is not going to happen.

 

[Erel]

Does it happen in Release mode as well?

 

[LucaMs]

Can be this the problem?

You shouldn't block the main thread

Use a Service?


[I know Erel does not agree, but... try adding a DoEvents inside the loop ]

 

[Erel]

Note that using a service will not help. Service code runs on the main thread as well.

 

[SinanTasgin]

Does it happen in Release mode as well?

Yes , I 'm having the same problem.

 

[LucaMs]

Note that using a service will not help. Service code runs on the main thread as well.

Yes, I thought about this after. Eventually, a new thread.

Anyway, given that adding a DoEvents takes 1 sec, I would try

 

[Erel]

The way to solve such issues is to add some log messages and find out where it hangs or takes too long to complete.

If you are dealing with large strings then you should use StringBuilder instead of String.

 

[SinanTasgin]

As shown in the photo section of the <details> to produce 1008 units.

Is it a problem XML string of overload ?

 

[LucaMs]

The way to solve such issues is to

... send the project to Erel

 

[Erel]

The correct way to build large strings is with a StringBuilder. We cannot really say to much without going over your code.
As I said before you should add some log messages to understand what slows down.

 

[KMatle]

I would write the xml to a FILE instead of using a string...

My opinion: Keeping huge data structures in memory is a programming mistake (>1000 units -> bad). For this we have files or databases.

XML is nice (I use it a lot) but keep an eye on the data/overhead ratio (does it make sense to store 4 bytes in a structure which needs 50 to keep it?)

 

[SinanTasgin]

Use StringBuilder instead of string expression in the program performance has increased.
The main thing that solves my problem also I had to add SetApplicationAttribute(android:largeHeap,"true") to the manifest editor.

Thank you to everyone.

https://www.b4x.com/android/forum/t...-to-check-memory-available.58925/#post-371102