Fixed UI freeze occurring when the queue finishes playback.

[Kwensiu]

As described, it is unclear whether this issue occurs on your device. On my device, it can be reproduced 100% of the time with the following steps:

1. Find a single-song album and start playing the album.
2. Set the playback mode to sequential playback (i.e., pause after the playlist ends), and wait for the song to finish playing.
3. UI freeze occurs, manifesting as an inability to switch pages/interfaces, although some animations may still be present. In some cases, the application may crash.

There are also related many warnings in DevTools, for example:

Waveform.svelte:219 Uncaught (in promise) TypeError: Cannot read properties of null (reading 'fileInfo') at Waveform.svelte:219:57 at <anonymous>:272:26 at Object.runCallback (<anonymous>:284:7) at value (<anonymous>:366:40) at <anonymous>:1:88 at <anonymous>:1:29821 (anonymous) @ Waveform.svelte:219 (anonymous) @ VM2566:272 runCallback @ VM2566:284 value @ VM2566:366 (anonymous) @ VM3059:1 (anonymous) @ VM3059:1

Solution: After consulting with AI, I was advised to add optional chaining ( ?. ) and fallback default values ( || 0 or || 1 ) for $current.song.fileInfo Following these modifications, UI freezing no longer occurs in my tests. It is unclear if there are additional locations that could cause the same issue.

[basharovV]

Nice thanks! I added a more explicit clearWaveform function when reaching the end of the queue (current.song is null). And instead of adding lots of optionals, it's probably cleaner to just return early from the function when we know that the song is null.

[Kwensiu]

Nice thanks! I added a more explicit clearWaveform function when reaching the end of the queue (current.song is null). And instead of adding lots of optionals, it's probably cleaner to just return early from the function when we know that the song is null.

Nice, This works on my device as well.