Support and General Use > Hardware
Clip Zip Divide by Zero 30083AC0
jhMikeS:
A regular, non-zero pattern fill of the entire audio buffer just before playback starts might help. It's hard to tell if the garbage was already there or filled-in by playback's file reading. Post a RAM dump of that.
jhMikeS:
Perhaps provide the very file as well, please?
saratoga:
Sorry thought you had this:
http://mit.edu/mgg6/www/crashes.7z
Edit: Playing the M4A in that folder structure generates the crash. Other structures do not necessarily (see dreamlayers comment above).
Edit2: The Zip and Fuze+ crash, but I could not get the Clip+ to.
jhMikeS:
--- Quote from: saratoga on April 28, 2015, 06:12:19 PM ---Sorry thought you had this:
http://mit.edu/mgg6/www/crashes.7z
--- End quote ---
I guess I missed that. I tried the direct m4a link and it wasn't working.
Does this only happen when the buffering of the mp3 starts (I don't think the first file will fit in its entirety)? I ask because I don't know if I'll be able to duplicate it because the closest device I have as far as memory size is a Fuze V2. My only AMS V1 is a clip with only 2MB.
I'm suspicious that it's low-level if it's specific to certain devices. It's worth mentioning here again that the newer file system code doesn't align buffers at the file API level, which already had side effects on another model but that was fixed up.
It's also possible that obeying POSIX more closely actually changed some expected return values/errnums.
Getting a sentinel-marked buffer dump would help me see if the last handle for the MP3 metadata isn't just being clobbered on account of over reading the previous M4A.
Well, I've got plenty of ideas of things to check but not much info yet to start ruling things out. Will get back...
saratoga:
Fuze v2 and Zip are nearly identical (same SOC, same memory, both color displays) so I expect it will happen on Fuze v2, but I don't have one to try.
There was also a report of an ALAC file that causes the same effect (crash post file system rework, fine before it), but I never got a sample to test so I didn't pay attention to it. Does the MP4 parser do something unusual compared to other codecs?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version