IPB

Welcome Guest ( Log In | Register )

> foobar2000 Tech Support Forum Rules

Please read foobar2000 Tech Support Forum Rules before posting and comply with all the points.
Failure to provide all the information pointed out in the above document in your post is considered wasting other people's time and in extreme cases will lead to your topic getting locked without a reply.


See also: Hydrogenaudio Terms of Service.

 
Reply to this topicStart new topic
Dynamic range scan on MLP tracks from DVD-A ISO hangs, was: "Bug in 1.1.10 - 1.1.12?"
Sandrine
post Apr 12 2012, 22:12
Post #1





Group: Members
Posts: 320
Joined: 2-July 10
Member No.: 81991



A really weird bug, but can be reproduced on my system 100%.

Installed (I have actually removed all other plug-ins when testing this):
- foobar2000 higher than 1.1.9
- foo_input_dvda 0.4.11
- foo_dynamic_range 1.1.1

When running a Dynamic Range scan on MLP tracks from a DVD-A ISO, foobar2000 will completely freeze 99% of the time. No crash log is written, the program can only be closed with Task Manager.

When using foobar2000, the problem almost goes away. Most scans will run through, but sometimes foobar2000 will hang at the very end when trying to write the tags. Trying to close foobar2000 then results in a message like: [The following tasks are active: tag writing. Changes will be lost when closing foobar2000]. A force-close is then necessary, too.

I can only guess that this has something to do with the way ISOs are locked when opened in foobar2000. I hesitate to blame the author of foo_input_dvda since the freezing behaviour is vastly different between foobar2000 versions.
Go to the top of the page
+Quote Post
marc2003
post Apr 13 2012, 00:05
Post #2





Group: Members
Posts: 4874
Joined: 27-January 05
From: England
Member No.: 19379



possibly related to this that was introduced in 1.1.11...

QUOTE (http://www.foobar2000.org/changelog)
Experimental deadlock detection (beta 2)

After long periods of apparent UI unresponsiveness, the application will automatically terminate and produce a crash report.


and another forum post i remember reading on the subject.... (click the little arrow to take you to the original thread)

QUOTE (kode54 @ Apr 1 2012, 20:21) *
Again, these are not crashes, per se. This is the deadlock watcher triggering. It means the main thread of the application was non-responsive for two full minutes.




Go to the top of the page
+Quote Post
Sandrine
post Apr 13 2012, 06:50
Post #3





Group: Members
Posts: 320
Joined: 2-July 10
Member No.: 81991



QUOTE (marc2003 @ Apr 13 2012, 00:05) *
possibly related to this that was introduced in 1.1.11...
QUOTE ([url="http://www.foobar2000.org/changelog)
Experimental"]http://www.foobar2000.org/changelog]Experimental[/url] deadlock detection (beta 2) After long periods of apparent UI unresponsiveness, the application will automatically terminate and produce a crash report.


Not sure... Dynamic range detection of SACD which takes even longer completes just fine.
Go to the top of the page
+Quote Post

Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

 



RSS Lo-Fi Version Time is now: 21st December 2014 - 00:09