search

google-code-export / mobbler

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

When submitting queue Mobbler crashes with USER 23 #694

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Hi there.

My beta version of Mobbler is crashing after I launch it, during the 
"Handshaking" process (status in upper right corner). The error codes are 
"Application closed: / Mobbler / USER 23" and "Application closed: / Mobbler 
CLF / USER 23" (the latest following the first).

My internet connection is totally OK, tried both wifi and 3g. The problem first 
started today, yesterday I used beta Mobbler without any issues. I also tried 
old Mobbler (stable), it is working properly.

Original issue reported on code.google.com by timofey....@gmail.com on 12 Nov 2010 at 7:52

GoogleCodeExporter commented 9 years ago 
USER 23:

"This panic is raised when any operation that moves or copies data to an 8 bit 
variant descriptor, causes the length of that descriptor to exceed its maximum 
length.

"It may be caused by any of the copying, appending or formatting member 
functions and, specifically, by the Insert(), Replace(), Fill(), Fillz() and 
ZeroTerminate() descriptor member functions. It can also be caused by the 
SetLength() function."

Original comment by hugovk@gmail.com on 12 Nov 2010 at 12:08

GoogleCodeExporter commented 9 years ago 
What phone are you using? What language is your phone in? Have you installed 
any language packs?

Original comment by hugovk@gmail.com on 12 Nov 2010 at 12:12

GoogleCodeExporter commented 9 years ago 
I am using Nokia 5530, software version 30.0.009 (31-05-10). My phone language 
is set to English, but it also has Russian, Ukrainian etc. I didn't install any 
"packs", though, it just was there from the beginning.

Original comment by timofey....@gmail.com on 12 Nov 2010 at 12:17

GoogleCodeExporter commented 9 years ago 
I would also like to add that I have some "queued" tracks in Mobbler's cache, 
as I've been using it without internet connection for some time (offline mode), 
and maybe this is the reason the app crashes trying to submit cached tracks to 
last.fm.

Original comment by timofey....@gmail.com on 12 Nov 2010 at 12:19

GoogleCodeExporter commented 9 years ago 
Is there any way I can clear up Mobbler's cache besides reinstalling the 
application?

Original comment by timofey....@gmail.com on 12 Nov 2010 at 1:05

GoogleCodeExporter commented 9 years ago 
You can export the queue to a file, that will clear it. See "Export Queue to 
Log" here:

http://code.google.com/p/mobbler/wiki/Instructions

Original comment by hugovk@gmail.com on 12 Nov 2010 at 1:36

GoogleCodeExporter commented 9 years ago 
Switched to offline mode, exported queue to log file, restarted and switched 
back to online - it works! Apparently, the problem was caused by queued data - 
Mobbler was crashing when submitting it.

Original comment by timofey....@gmail.com on 12 Nov 2010 at 1:59

GoogleCodeExporter commented 9 years ago 
Good news! Do you still have the C:\Data\Mobbler\.scrobbler.log file? If so, 
please could you upload it here so we can check what was causing the problem?

Original comment by hugovk@gmail.com on 12 Nov 2010 at 2:28

GoogleCodeExporter commented 9 years ago 
Sure thing! Here it is. Please note that all of the metadata is in Cyrillic 
characters.

Original comment by timofey....@gmail.com on 12 Nov 2010 at 2:40

Attachments:

GoogleCodeExporter commented 9 years ago 
Aha, the problem will be due to Mobbler not sending Cyrillic characters 
properly then. Thanks!

Original comment by hugovk@gmail.com on 12 Nov 2010 at 2:46

GoogleCodeExporter commented 9 years ago 
And thank you!

Original comment by timofey....@gmail.com on 12 Nov 2010 at 2:51

GoogleCodeExporter commented 9 years ago 
I just tried to reproduce by setting a test mp3 to use metadata of the first 
entry from the log:

1. play song when offline
2. wait until it finishes
3. go online

I also tried using the metadata from the last two entries. But in each case the 
song scrobbled as expected. If you see it again, let me know and we could try a 
version with extra logging.

Original comment by hugovk@gmail.com on 12 Nov 2010 at 4:40

GoogleCodeExporter commented 9 years ago 
Same problem here, after 12 tracks scrobbled offline. Once exported the log and 
restarted Mobbler, it won't crash when going online.
Using Mobber 0.10(80) on a Nokia 5800XM, Firmware 50.0.005, RM-356, Product 
Code 0575581, italian localization (both Phone and Mobbler).
I'm attaching the log file, it doesn't look like there's any extended character 
in it.
I hope this helps anyway...

Original comment by maurizio...@gmail.com on 13 Nov 2010 at 3:02

Attachments:

GoogleCodeExporter commented 9 years ago 
Same here. Crash while handshaking. When songs are in the queue to be scrobbled

Original comment by Nicholas...@gmail.com on 14 Nov 2010 at 1:58

Attachments:

GoogleCodeExporter commented 9 years ago

Original comment by hugovk@gmail.com on 14 Nov 2010 at 9:52

GoogleCodeExporter commented 9 years ago 
I wonder if it's to do with queue size. The three examples here are 19, 12 and 
13 tracks longs. Do you get it with shorter size queues?

I've only been scrobbling short queues, I'll try some longer ones.

Original comment by hugovk@gmail.com on 23 Nov 2010 at 9:17

GoogleCodeExporter commented 9 years ago 
Issue 695 has been merged into this issue.

Original comment by hugovk@gmail.com on 23 Nov 2010 at 10:00

GoogleCodeExporter commented 9 years ago 
OK, I can reproduce it with 14 tracks. The crash is coming from these two lines 
when apiSig eventually becomes longer than 1024 whilst adding the data for 
*all* the queued artists, albums, duration and so on in a single form:

http://code.google.com/p/mobbler/source/browse/src/mobblerwebservicesquery.cpp#1
56

This particular function hasn't changed in ages, so it must be the way it's 
being used for the new scrobble API.

Original comment by hugovk@gmail.com on 23 Nov 2010 at 10:37

GoogleCodeExporter commented 9 years ago 
This line in my .scrobbler.log file kills the upload.

El�el�set     Humppamaratooni Humppapotilas   0       100     L       
1289920168

I've listened to Eläkeläiset a lot in the past (they are the top band in my 
last.fm library), so they used to work.

Original comment by phess...@gmail.com on 24 Nov 2010 at 6:55

Attachments:

GoogleCodeExporter commented 9 years ago 
Fixed in r536981c901 and r386289c094. It will be released in the next version.

Thanks everyone for the reports, this is exactly what beta testing is for.

Original comment by hugovk@gmail.com on 24 Nov 2010 at 1:35

GoogleCodeExporter commented 9 years ago 
Will we need to flush our queue, or will the current queue be fixed when we 
upgraded?

Original comment by phess...@gmail.com on 24 Nov 2010 at 1:54

GoogleCodeExporter commented 9 years ago 
No need to flush the queue, it will be submitted properly with the next version.

Original comment by hugovk@gmail.com on 24 Nov 2010 at 2:34