7170 Unable to Play Folder ...

[MourningStar]

... hangs in open folder dialog, only first file loads & plays and dialog will not close. TM shows 'not responding' and must end task. Single files and streams play ok.

[dro]

There's an issue affecting a small number of users from what I can see from the 7170 crash reports which never appeared from the beta testers where a deadlock / hang occurs when the main playlist editor is trying to obtain the title to show for newly added items.

The triggers seem to either be when starting playback (which is why it's odd it's not shown up from the beta testers or my own usage) or when doing a batch import. Thankfully I've got a number of good crash reports showing the points that seem to be cause of the deadlock to work with to get this resolved.

-dro

[MourningStar]

There's an issue affecting a small number of users ...  which never appeared from the beta testers ...

Perhaps it is due to only a 'small number of users' is all that play entire folders and/or with sub-folders? If not, oh well, too many other variables may be the cause. In any case, selecting all tracks in a single folder works for me until the fix surfaces. -thx

[MourningStar]

p.s. where can i find the crash report on my pc?

[dro]

From what I see it's happening due to at least 2 different ways including non-modified playlists where it's been left to play as a result of 2 different parts trying to get / update at the same time & due to the protection in place, it causes a deadlock which then causes the UI to enter a hung state & then *boom* it triggers the unresponsive crash handler (especially if the user starts to click on things as is how the OS handling in that state goes).

Preferences -> Advanced -> Error Reporting -> there's a clickable link to open the crash reports folder.

-dro

[MourningStar]

^
appears a previous issue i had may be related?

https://getwacup.com/community/index.php/topic,1072.msg6433.html#msg6433

[dro]

Nah, that isn't what's being experienced.

-dro

[Cosa]

This issue looks to be fixed in the build 7236 release.

[dro]

Thanks for the confirmation. This seems to match with the lack of any crash reports from 7236 installs related to the issue

-dro