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: Crash when attempting to read files from HFS+ partition (Read 7730 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Crash when attempting to read files from HFS+ partition

Hello,

I have an iMac which dual boots Windows and Mac OS X, using Apple's Boot Camp. When I upgraded to Windows 7 today I decided to move my music to OS X's HFS+ partition, so that I could reformat the Windows one. The HFS+ partition is accessible within Windows since Boot Camp 3.0, but whenever I try to add any music from it to my playlist, my fresh install of foobar2000 1.0b5 crashes.

See here: http://img121.imageshack.us/img121/7417/fbcrash.jpg

I also tried version 0.9.6.9 of fb2k, previous to this; it doesn't crash, but does not add the music to the playlist either (seemingly ignoring the files altogether.) Inferior music players such as WMP seem to have no difficulty with the files.

I did not get an option to send a crash report to the foobar2000 developers, only to Microsoft as usual. Obviously the simple solution is to move my music back onto the Windows partition, but I thought I would make a report nonetheless. If there's any more information I can provide that might help solve this issue, please let me know.

Crash when attempting to read files from HFS+ partition

Reply #1 –
Also reproes for me. I fired up Process Monitor and it looks like foobar got stuck on .DS_Store file - trying to enumerate it recursively as a directory or something like that.
There are LOTS of entries like D:\\\\\.DS_Store\* .. etc.
Note that Process Monitor does not show paths correctly on HFS+ for some reason, so those '\\\\' is probably a valid path..
Also, first API call on the stack after foobar2000 is FindFirstFileW

EDIT:
(1094.1338): C++ EH exception - code e06d7363 (first chance)
(1094.1338): Stack overflow - code c00000fd (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
eax=00000064 ebx=005d0000 ecx=005d7484 edx=000000b6 esi=005d0244 edi=05ea339c
eip=773edd7e esp=05ea2fac ebp=05ea3020 iopl=0        nv up ei pl nz ac pe nc
cs=0023  ss=002b  ds=002b  es=002b  fs=0053  gs=002b            efl=00010216
ntdll!memcpy+0xba7e:
773edd7e 53              push    ebx
0:005> kv
ChildEBP RetAddr  Args to Child             
05ea3020 773edf72 05ea339c 05ea33c4 05ea395c ntdll!_SEH_prolog4+0x1a
05ea3094 7741a612 005d0000 00000000 000000b6 ntdll!RtlAllocateHeap+0x206 (FPO: [3,24,0])
05ea30b0 77421203 05ea30f4 05ea33d0 05ea33c4 ntdll!RtlpWin32NTNameToNtPathName_U+0x39 (FPO: [4,1,4])
05ea3314 773fa793 00000001 05ea3334 05ea33d0 ntdll!RtlpDosPathNameToRelativeNtPathName_Ustr+0x79 (FPO: [5,145,0])
05ea333c 774014e2 00000001 020bcfe0 05ea33d0 ntdll!RtlpDosPathNameToRelativeNtPathName_U+0x5f (FPO: [5,2,4])
05ea3358 76d695d5 020bcfe0 05ea33d0 05ea33c4 ntdll!RtlDosPathNameToRelativeNtPathName_U+0x18 (FPO: [4,0,0])
05ea3648 76d69c2a 020bcfe0 00000000 05ea36d8 KERNELBASE!FindFirstFileExW+0x9f (FPO: [6,179,4])
*** ERROR: Module load completed but symbols could not be loaded for C:\Program Files (x86)\foobar2000\foobar2000.exe
05ea3668 00272b6f 020bcfe0 05ea36d8 0202cb64 KERNELBASE!FindFirstFileW+0x16 (FPO: [2,0,0])
WARNING: Stack unwind information not available. Following frames may be wrong.
05ea3938 00337e14 067ac750 05ea39a8 0202cb64 foobar2000+0x42b6f
05ea3974 00340668 067ac750 05ea39a8 0202cb64 foobar2000+0x107e14
05ea39e4 003406c4 067ac750 05ea3a48 02118dc4 foobar2000+0x110668
05ea3a60 003406c4 067ac6e8 05ea3ac4 02118dc4 foobar2000+0x1106c4
05ea3adc 003406c4 067ac680 05ea3b40 02118dc4 foobar2000+0x1106c4
05ea3b58 003406c4 067ac618 05ea3bbc 02118dc4 foobar2000+0x1106c4
05ea3bd4 003406c4 067ac5b0 05ea3c38 02118dc4 foobar2000+0x1106c4
05ea3c50 003406c4 067ac548 05ea3cb4 02118dc4 foobar2000+0x1106c4
05ea3ccc 003406c4 067ac4e0 05ea3d30 02118dc4 foobar2000+0x1106c4
05ea3d48 003406c4 067ac478 05ea3dac 02118dc4 foobar2000+0x1106c4
05ea3dc4 003406c4 067ac410 05ea3e28 02118dc4 foobar2000+0x1106c4
05ea3e40 003406c4 067ac3a8 05ea3ea4 02118dc4 foobar2000+0x1106c4

Crash when attempting to read files from HFS+ partition

Reply #2 –
Quote from: hlt on
I fired up Process Monitor and it looks like foobar got stuck on .DS_Store file - trying to enumerate it recursively as a directory or something like that.
There are LOTS of entries like D:\\\\\.DS_Store\* .. etc.
Could you please provide some more detailed parts of the Process Monitor log? How the enumeration of the directory with .DS_Store goes from the start, what attributes were reported for that file, etc.
Full-quoting makes you scroll past the same junk over and over.

Crash when attempting to read files from HFS+ partition

Reply #3 –
Quote from: Yirkha on
Could you please provide some more detailed parts of the Process Monitor log? How the enumeration of the directory with .DS_Store goes from the start, what attributes were reported for that file, etc.

Well, I captured the log but after that I noticed one interesting thing - running 'dir' command in cmd on that HFS+ volume also crashes CMD. I don't think you should waste any dev time on a workaround for what seems to be an Apple product bug (do they even have QA in their Windows division?)

Apple-only repro (disk E - HFS+ with BootCamp driver): cmd /C dir e:

Crash when attempting to read files from HFS+ partition

Reply #4 –
I might be able to workaround this regardless; while this is a case of directory enumeration returning nonsense, we shouldn't allow path recursion that actually keeps enumerating contents of the same folder over and over.
Is there anything else interesting in the process monitor log than parsing of paths with duplicated slash characters?
Microsoft Windows: We can't script here, this is bat country.

Crash when attempting to read files from HFS+ partition

Reply #5 –
i´m interested in this case either. same problem here. windows7 64-bit, bootcamp 3.0. apple will come with an update for bootcamp. i don´t know if this will fix the problem.

theoretical: do i understand it right, that foobar should have no problems to "just" read for a HFS+ drive?

Crash when attempting to read files from HFS+ partition

Reply #6 –
Quote from: Peter on
Is there anything else interesting in the process monitor log than parsing of paths with duplicated slash characters?

Does not look like there is;
here's the zipped ProcMon log during the crash

Here is an archive with .dmg and .vmdk of an HFS+ partition with a single music file, it's enough to repro. BootCamp.msi fo x86 and x64 also included (BootCamp.msi includes HFS drivers) >>>
.dmg is a raw 100mb disk image, .vmdk is the same image written to VMWare-format virtual disk (I'm assuming everyone has VMWare, heh)

EDIT: to repro with attached HFS+ partition, just drag and drop the only music folder on the partition into foobar and wait for the crash -)
 

Crash when attempting to read files from HFS+ partition

Reply #7 –
Does 1.0 beta 6 still crash for you? I added a simple workaround to ignore returned folder names that consist only of dots or slashes.
Microsoft Windows: We can't script here, this is bat country.

Crash when attempting to read files from HFS+ partition

Reply #8 –
Quote from: Peter on
Does 1.0 beta 6 still crash for you?

Yes; I didn't look at the stack this time (it's way too boring without symbols), but it looks exactly the same. Heh, since there's a cmd-only repro, something is definitely fucked up with this driver code... I'm actually amazed it hasn't bluescreened so far yet..

I can PM you with a remote (RDP) to my repro box to make your life a bit easier, if that helps.
Otherwise, just installing Microsoft trial of Win7 into VMWare and connecting vmdk from the previous post will give you a repro environment.

Crash when attempting to read files from HFS+ partition

Reply #9 –
i don´t know if this helps, but i think apple driver are really some sort of buggy.

i get sometimes even a blue-screen in win 7 by just hoovering a open explorer-window (that shows a mac-partition) with some files. not that my intention was to place this files on that mac-partition, i´m just "on my way" to recycle-bin for example, move those files over that open explorer-window and get a blue-screen.

hopefully the upcoming update of bootcamp 3 will fix this.

don´t know if this helps you.

Crash when attempting to read files from HFS+ partition

Reply #10 –
ok, today apple released new bootcamp driver 3.1; with them access to HFS+ partitions inside of windows7 works 100%.

now the sad fact related to foobar v1.0: still programm-crash when read from HFS+ partition. PLEASE HELP!

Crash when attempting to read files from HFS+ partition

Reply #11 –
could someone from the foobar dev-team post a quick note here about this problem.
just something like "not a foobar problem", "apple´s driver fault", "problem could be fixed, but we have no time for that now", "problem is not fix-able", ... just something.

i´m not a coder and don´t understand this problem; windows can read HFS+, so wonder why foobar crash by trying this.
i guess i´m not the only one who is curious. thank you.

Crash when attempting to read files from HFS+ partition

Reply #12 –
The HFS+ driver by Apple behaves differently than standard Windows ones do. QueryDirectoryInformation command for an invalid path on a HFS+ volume returns ERROR_FILE_NOT_FOUND (The system cannot find the file specified.) instead of ERROR_DIRECTORY (The directory name is invalid.), which can confuse applications. Note a simple "dir E:\" in Command Prompt results in a crash too, says something about how robust the product is.

Nevertheless there will be additional workaround for this problem in a future version.
Full-quoting makes you scroll past the same junk over and over.

Crash when attempting to read files from HFS+ partition

Reply #13 –
Quote from: Yirkha on
...Nevertheless there will be additional workaround for this problem in a future version.

that would be real great!
thank you for your answers.

Crash when attempting to read files from HFS+ partition

Reply #14 –
Unnecessary reply, but this is also occurring for me.
For anyone getting frustrated about this, if you have enough HDD space, just copy the music files over to the other partition first, then drag them into foobar.

Crash when attempting to read files from HFS+ partition

Reply #15 –
Just to confirm, the same is happening to me. Windows XP SP3 on bootcamp 3.1, latest fb2K. Works great when importing from NTFS/FAT32 disks but same files would not import from HFS+ partition (even though it's readily accessible under bootcamp).

And copy paste will not work for my library of 2T songs...

Crash when attempting to read files from HFS+ partition

Reply #16 –
I'm getting the exact same problem. nice to see that attempts are being made to work around this problem, but looks like i'll have to resort to iTunes for my music for the time being (gag)

Crash when attempting to read files from HFS+ partition

Reply #17 –
admins, mods, any news about progress in development about that problem?

Crash when attempting to read files from HFS+ partition

Reply #18 –
Why not ask Apple? It's their bug.

Crash when attempting to read files from HFS+ partition

Reply #19 –
i installed MacDrive, now the problem is resolved. as long as it works i'm happy

Crash when attempting to read files from HFS+ partition

Reply #20 –
i tried foobar 0.83 ,and it works fine,but my foobar 0.96 doesn't.