Skip to main content

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: Incompatible cuesheet playback attempt = crash (Read 868 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Incompatible cuesheet playback attempt = crash

Tested just now with 1.2.2, bug still present.

I have a cuesheet here which is obviously malformatted - every track has two indexes (ok) but all the times of index 01 are 00:00:00 when they should be momentarily after index 00.

This appears to be making foobar baulk and divebomb; every playback attempt results in an instant crash as it parses the cuesheet. Curiously it gets to track 3 before the parser gives up -- it displays the error "Unable to open item for playback (Error parsing cuesheet: invalid index list (line 18)):
"C:\path\to\cuesheet.cue"

Then the program quits and offers to let me see the crash log.

Related -- I've noticed quite a few times when fb2k does crash that the playback error box opens but then the main application crashes and takes the (helpful) error box with it. Is there no way to invoke the playback error dialog box as a separate process (in the case of the main player crashing), or handle exceptions slightly more gracefully?

I think I've only been able to make fb2k crash intentionally about half a dozen ways to date, most of which involve streaming or funky file formats (or formats which aren't what they seem) so on the whole I'm very happy.
Don't forget International Talk Like A Pirate Day! September the 19th!

 

Incompatible cuesheet playback attempt = crash

Reply #1
Thank you for the bug report.
Please autosubmit a crash report then post again on the forum so I can identify the report by your IP address and look into it. I do not see any logged reports for your current IP address.
Microsoft Windows: We can't script here, this is bat country.