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
Bug: crashing when using search and garbage characters when updating t
xska
post Nov 18 2012, 12:50
Post #1





Group: Members
Posts: 8
Joined: 28-December 05
Member No.: 26702



Hi,

I've submitted about a dozen of different crash reports as the library search stopped working for me. I think it only started with 1.1.17, but I have tried going back to .16 and it did not help.

Another bug is that when I use RG scanner and then update tags it doesn't write the tags properly and puts garbage into track numbers, like this:

A few more things I have noticed: any tag update on MP3 files is broken (bad characters, etc); everything works fine for AAC-encoded files.

Before updating:

After:

Properties after:


This post has been edited by xska: Nov 18 2012, 13:02
Go to the top of the page
+Quote Post
Peter
post Nov 19 2012, 15:18
Post #2


foobar2000 developer


Group: Admin
Posts: 3307
Joined: 30-September 01
Member No.: 84



QUOTE (xska @ Nov 18 2012, 12:50) *
I've submitted about a dozen of different crash reports as the library search stopped working for me. I think it only started with 1.1.17, but I have tried going back to .16 and it did not help.
Tried making a completely clean foobar2000 install (eg. separate portable install) without thirdparty components? I've seen the reports already but they're not making a whole lot of sense, the code that crashes is in Windows DLLs, not in something that I have any power over; it's breaking while performing a trivial task of building a map of non-ASCII characters to their most similar ASCII equivalents (using WideCharToMultiByte).

QUOTE
Another bug is that when I use RG scanner and then update tags it doesn't write the tags properly and puts garbage into track numbers, like this

A few more things I have noticed: any tag update on MP3 files is broken (bad characters, etc); everything works fine for AAC-encoded files.
It would be very helpful if I could have a look at one of your files, before + after the bad tag update. [ hint: uploads forum ]

Finally: is there anything specific regarding your regional & code page settings in Windows control panel? Perhaps the two issues are in fact different symptoms of the same.
Go to the top of the page
+Quote Post
xska
post Nov 19 2012, 19:47
Post #3





Group: Members
Posts: 8
Joined: 28-December 05
Member No.: 26702



I will try a clean install to see if it helps.

Here are my regional settings and here is the topic with with uploaded files (before and after update). Let me know if you need anything else.





This post has been edited by xska: Nov 19 2012, 19:48
Go to the top of the page
+Quote Post
xska
post Nov 19 2012, 19:55
Post #4





Group: Members
Posts: 8
Joined: 28-December 05
Member No.: 26702



I did a fresh installation using portable mode option and into a separate directory but unfortunately it does the same with the track numbers whenever any MP3 file is updated

This post has been edited by xska: Nov 19 2012, 19:55
Go to the top of the page
+Quote Post
Peter
post Nov 19 2012, 21:24
Post #5


foobar2000 developer


Group: Admin
Posts: 3307
Joined: 30-September 01
Member No.: 84



FYI, upload topic hidden since I have the files, no reason to share them with anyone else.

Issue being investigated, thanks for the report.
Go to the top of the page
+Quote Post
Peter
post Nov 20 2012, 10:26
Post #6


foobar2000 developer


Group: Admin
Posts: 3307
Joined: 30-September 01
Member No.: 84



Have you installed any other software recently just before the issue appeared?

As far as I can tell, WideCharToMultiByte part of the Windows API is acting nonsensically on your system; either crashes or produces incorrect output (hence bad tags).

The crash report tracker says there's exactly one more user (one report logged last month) having this issue; so it's not just your system but it's something extremely obscure and it never triggered until recently - perhaps some third party app has something to do with it?

I can only recommend that you do not use foobar2000 until this issue is somehow resolved; various parts of foobar2000 codebase rely on this function and will produce incorrect output.
Go to the top of the page
+Quote Post
mudlord
post Nov 20 2012, 11:01
Post #7





Group: Developer (Donating)
Posts: 818
Joined: 1-December 07
Member No.: 49165



Also, do a virus scan.
Some viruses add DLLs into every process to do hooks like this.
Go to the top of the page
+Quote Post
xska
post Nov 20 2012, 21:46
Post #8





Group: Members
Posts: 8
Joined: 28-December 05
Member No.: 26702



Well, there was a bunch of Windows updates recently (last Tue) - that was just before the issue started happening. Also there was a QuickTime update as well. But other than that, nothing new installed.

I did a virus scan and malware scan - all clean.

I have also tried changing my locale to English-UK and to English-US but it did not help. The most strange thing is why does it work correctly for AAC files? What's the difference?

Another manifestation of this bug is that foo_dop stopped working correctly and is now unable to upload most of the files onto my iPod. That used to work fine too.
Go to the top of the page
+Quote Post
Peter
post Nov 20 2012, 23:15
Post #9


foobar2000 developer


Group: Admin
Posts: 3307
Joined: 30-September 01
Member No.: 84



WideCharToMultiByte is used for converting Unicode text to non-unicode (specific codepage), which is needed for specific ID3 tag fields. This is not needed for MP4/AAC tags where all the data is Unicode all the time.
Go to the top of the page
+Quote Post
xska
post Nov 21 2012, 00:09
Post #10





Group: Members
Posts: 8
Joined: 28-December 05
Member No.: 26702



I have managed to track this issue down to a corrupted NLS file at c:\windows\system32\C_20127.NLS (thank god for SysInternals tools!). Once I restored the file from original Win7 CD everything is back to normal. Many thanks for looking into this - I would not have been able to find the culprit broken file without your hints.

I have no idea how it got corrupted in the first place though. Also strange that no other applications use this code page, seems like only Foobar was affected.

This post has been edited by xska: Nov 21 2012, 00:12
Go to the top of the page
+Quote Post
Peter
post Nov 21 2012, 10:28
Post #11


foobar2000 developer


Group: Admin
Posts: 3307
Joined: 30-September 01
Member No.: 84



Good to know that it's fixed.

I guess few apps rely on WideCharToMultiByte this much, in fb2k it's needed essentially for the stuff that broke for you (ID3 tag handling + character remapping in search queries).
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: 28th November 2014 - 17:52