ceene | # 1171 | 2015-09-19, 10:23 | Report

Can you send me your log reflecting this? That is not normal, as Yappari always tries to reconnect. It may happen, however, that it crashes completely. That is known to happen but it is thought to be a bug in the underlying code, i.e. QT, not in Yappari tself.

s4br0s0 | # 1172 | 2015-09-19, 10:23 | Report

When says: "Trying to reconnect in 10 sec", does that and if you're connection is good (that happens usually on 2.5g, maybe on 3g, really wierd on wifi), reconnects as log in.

When says: "Disconnected", does not reconnects, basically crash the app for "unknow" reasons, and you have to manually reconnects.

So there are two differents stuff that you mention, one it does what you want, the second doesn't cause the app crash.

You're problem have to be with poor signal.

Greetings.

n900_man | # 1173 | 2015-09-19, 11:49 | Report

http://talk.maemo.org/showpost.php?p...postcount=1160

Yes, It crashes completely. You mean problem is in Qt library? Mabye its bug somewhere in Yappari... Maybe I must add more diagnostic log messages in codebase and test yappari with them to find more info...


Yes, I often have bad poor signal... What caused app to crash when signal is poor? Maybe some timers are out of time when waiting for packets..

Thanks for help

ceene | # 1174 | 2015-09-19, 12:32 | Report

Sorry, I must have missed your previous message. That log is unfortunately too short, although from latest message from Cepiperez I can solve at least the stream:error message, but a more complete log would be useful.

The crashes are undoubtedly a problem outside Yappari, even the coredumps are corrupted. I've tested it with a debug enabled version of Yappari and it seems clear. There can be, however, some way to avoid this crashes, but I've yet to found them.

Please, try to send me a log in which those disconnect occur and in which an INCOMING <notification> is received.

I'll be releasing 2.0.21 soon and will explain with it everything that has happened during the last two weeks, it's been pretty intensive.

s4br0s0 | # 1175 | 2015-09-19, 12:44 | Report

Not 100% sure but the disconnect have to be with groups incoming message, almost every tiime i got the disconnect crash, when connects again, recieve a (or several) gruop message(s).

Sometimes i suspect that is just something with WA server.

Anyway, waiting for the next realese.

Greetings.

Carlotic | # 1176 | 2015-09-19, 16:42 | Report

Finally am part and parcel of the maemo community, it was difficulty getting registered. First and foremost i would like to give special thanx to ceene ooh u are truely our hero in the survival of nokia n900. Yappari is just awesome. Many thanx again to th rest of developers who are making contributions to the success of these fantastic apps. I howervr facing a problem maybe a bug i dont knw, i have YAPPARI 2..0.20 upgraded via repos in app manager, but since version 2.0.14 my yappari has been crashing 3-5 minutes of each successful login via either gsm, dual mode or 3G network but works perfectly fine via wifi network and doesn't crush at all.
I have seen threads about yappari saying connection closed by server, but thats not an issue to be worried about coz immediately after that notification yappari always get connected.
Plz if anyone cn tell what am missing, the help is greatly appreciated

handaxe | # 1177 | 2015-09-19, 21:25 | Report

@Carlotic - that sounds like what was being discussed in the previous 4 or so posts: crashes due to poor connection quality, typically GPRS

enne30 | # 1178 | 2015-09-20, 09:05 | Report

hi ceene, I'm getting bunch of "stream:error", too.
This evenience usually leads yappari to crash in a couple of minutes.
I'll try to be more specific:

- during a session first I got 2 stream errors after "receipt delivering" stuff -> stream_error_00.txt, stream_error_01.txt

- then I got 3 stream errors after get_groups_3 -> stream_error_02.txt

- finally I see a fatal get_groups_3 -> no stream error, but IO error and "Invalid length 0x8"

please note:
- 39330****** is me
- 39338******* is another yappari client (dunno if having other yappari contacts could be related to stream error problems)


EDIT : updated since this morning to 2.0.21 and so far no more "stream:error" in log nor crashes! Thank you ceene!!

Attached Files

	stream_error_00.txt (1.3 KB, 49 views)
	stream_error_01.txt (759 Bytes, 54 views)
	stream_error_02.txt (1.0 KB, 55 views)

---

Last edited by enne30; 2015-09-22 at 07:23.

Anna83 | # 1179 | 2015-09-21, 07:13 | Report

Thanks
But I'll try the first option.

enne30 | # 1180 | 2015-09-22, 15:29 | Report

bump!

latest version (2.0.21) seems again very stable, running for 10 hrs without crashes!