ANR after clicking 3 dots and "Details" in expanded now playing screen

Issue description:

I just came across a ANR suddenly when i was listening to a song (.m4a) file. When I clicked on the details tab in the 3 dots menu, the app froze for like 5-7 seconds and crashed.

Logs:

Upload description: ANR-AA-logs-with-song - description for the files uploaded.

EDIT: Forgot to mention that I have also included the ANR.trace file

Additional information:

 
Android Version: 12
Symfonium Version: 11.0.0
 

Reproduction steps:

 
1.) Play a .m4a song.
2.) Click on the 3 dots near the repeat mode selector.
3.) Click on details tab and the app freezes and crashes.
 

Media provider:

Box

Screenshots:

 

    

Your phone seems to have ran out of memory and locked the garbage collector.

This is strange that it locked it for so long and the trace shows that Symfonium does not use much memory either.

Hmm. I have restarted my device and the same issue occurs. Idk what to do now, any tips that might help? :smiling_face_with_tear:

You mean on that media each time? Any media?

Provide a full bug report: Capture and read bug reports  |  Android Studio  |  Android Developers

I see that the recently added 2 songs make the app crash, rest of the songs normally display the info without crashing.

Alright I’ll send the bug report by tomorrow as soon as I can. Got to go sleep now💤

And if you press 3 dots details in the normal song list without anything playing ?

It opens then freezes and crashes. I saw that it shows “disc: -1” in tag info if that helps.

No the disc is irrelevant, but there’s no media format data, so it’s probably ffmpeg that triggers that.

But since it works fine here it’s not the file, so the bug report may show something.

Alright. I’ll upload the bug report.

I’ve uploaded the zip file with the description: [email protected]

I may be wrong with the bug report as it is my first time doing it and couldn’t find how to capture one on a realme device online and neither does it have a capture bug report option.

Hopefully it’s what you’ve asked for, do let me know if you need anything more.

Then what have you done? The bug report must be from the device just after the issue.

I followed this post on realme community to generate the bug report. It’s from the device that has the issue. Third party apps and then captured the logs.

edit: my bad, In the above reply I said I didn’t find steps online.

Well does not show much :frowning:

Have you enabled the waveform are the waveform and the media info visible in the now playing ?

I had waveform enabled for like 2-3 days then disabled it. Media info shows MP4/AAC 512kb/s 44.1 kHz like in the screenshot below. :smiling_face_with_tear:

I re-enabled the waveform and I can see it. I tried again to click on details or long press on the media info but it still crashes.

Have you enabled high res image settings ?

The images in the file is very large, wonder if like the image does not fit in the memory cache and your phone can’t handle loading it multiple times.

Nope, high res images are disabled.

Just to be sure, I removed the song and replaced the song having large cover size to a much smaller one and synced it but it still crashed.

I also observed that it only crashes with AAC file. The original FLAC file opens details without any issues or crashing.

This makes no sense since you can play them and the media info and the waveform are properly extracted.

Can you provide a new set of logs with the file with lower image.
And maybe test with no image at all?

And maybe also without any tags at all?

And store the file locally ?

And anything you might think about :slight_smile:

Yes. I’ve uploaded the new logs and the low filesize replaced song file with the description: AA-new-logs-with-song

I have tested with no image at all and it works perfectly, it doesn’t crash. :star_struck:

I guess the low image was badly tested and cached somewhere then.

If you can try again with a small image and a completely different name.

I tried the small image again and as you’ve said renamed it without spaces and now it doesn’t crash lol. It’s now working properly.

Didn’t know an image could do this :upside_down_face:

Thank you so much for your help and understanding, really appreciate it :face_holding_back_tears: