"Assertion failed!"

[smokeanthrax]

hi! to preface this, i'm running foobar v2 beta 29, columns ui and windows 11. i've consistently been having this issue with coverflow even after two clean uninstall/reinstalls. it'll work fine for a bit, and then suddenly display this error.

aborting or retrying will make foobar crash. ignoring it will close the error, but it instantly pops up again. i can ignore the error (as in, actually ignore it) and continue using foobar and coverflow normally.

this wouldn't be a huge issue, as i can continue to actually use the program, but trying to load any past Columns .fcl themes, or change coverflow's display font, will make foobar lock up and crash. now, if i launch foobar in safe mode after a crash and uninstall coverflow, i can load themes again, but reinstalling coverflow just makes the perpetual error screen reappear. i'm at a loss. i know that cleanly reinstalling foobar remedies the issue, but that's an incredibly tedious process with how huge my music library is.

• i don't know if this is a coincidence or not, but i noticed that every time the error began appearing, it was soon after i exported a theme for the first time. i haven't tested this, but i have a hunch that the issue wouldn't occur if i dont export a theme at all.

is something wrong on my end? let me know if you need any more details (other components, etc). i would really appreciate any help. thanks!

edit: trying to remove a panel and then replace it with another will also make foobar crash... uninstalling coverflow fixes this

[Chronial]

This seems to be this bug in the image loading library I'm using: nothings/stb#628

Looks like this is caused by a special kind of bmp file. It might be embedded as art in one of your media files. Maybe you can identify which file is causing this issue and remove the image or convert it to another format.

Otherwise you will have to wait for me to upgrade the image loading library and release a new version of foo_chronflow, which might take a while :).

[smokeanthrax]

damn lmao. didn't think i had any .bmp files, i'll look for the offending files later today

thanks for the prompt response!