Clip Browser Crashing
 

Hopefully this is the right forum. Whenever I have a SD card mounted on my mac, Clip Browser crashes on launch. I've tried trashing preferences, repairing permissions, and reinstalling the program. If I copy the card to a hard drive (and unmount the SD card) Clip Browser works perfectly and I can access the files just fine. Any ideas?

A little more information...

MacOS 10.6.2
Clip Browser 2.06.00 (155.188)

Part of the crash log...

Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000
Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Application Specific Information:
*** Terminating app due to uncaught exception 'NSRangeException', reason: '*** -[NSCFString substringToIndex:]: Range or index out of bounds'

Anyone else having this problem?

It doesn't seem like anyone else has this problem, it could be a USB problem in your OS. Have you tried an external card reader?

How are you mounting the cards?

I have no problems with using my Express34 slot with the M+R adapter.

I have had problems with some Express 34 CF readers, they will crash the Mac.

I have not had any problems so far with USB card readers.

I too am on 10.6.2.

Sometimes you have to just go with what works. So many drivers from so many different sources.

It looks like Clip Browser doesn't like my SanDisk card reader. If there's a card mounted through it, then Clip Browser instantly crashes on startup. It used to work just fine, so I'm going to revert to an older version of Clip Browser and see if that makes a difference.

I tried a eFilm reader and it worked just fine, so I'm not sure if it's a problem with the card reader or a bug in the program. I tried the SanDisk reader on a different computer and Clip Browser also crashed, so it's not just that one computer.

What SD card readers are people using?

Have you tried launching ClipBrowser first and then putting in a card, or are you launching CB with a card ready to go?

I have a cheap card reader which was purchased for £14 from Jessops. I do have some older readers but these do not read SDHC cards. You should ensure that your reader will read SDHC, otherwise it won't work.

Same thing is happening to me
Version 2.06.00 (155.188)
MacPro Early 2008 OS 10.6.2
ClipBrowser crashes when I have my Sandisk card reader attached to any USB port. Remove the reader and ClipBrowser opens without issue.

Under a new user it still crashes so it is System related.
Given Sandisk reader has no installed drivers my guess is ClipBrowser in conflicting with some Apple OS USB related component.
The Sandisk reader by itself doesn't cause the crash. A card must be installed.
That would mean it has to do with something about how ClipBrowser is scanning "active" devices.

It's specific to the model of the reader!
My old
Sandisk ImageMate 12 in 1 Reader
Model Number SDDR-89 V4
Works fine. NO CRASH!
Amazon.com: SanDisk ImageMate 12-in-1 USB 2.0 Flash Memory Card Reader SDDR-89-A15: Electronics

My new Sandisk ImageMate All-in-One
Model Number SDDR-189-A20
Causes the crash when media is installed.
CompactFlash® Card Reader - Transfer Data Fast and Easy | SanDisk

How very strange given that there are no drivers installed with the device. Apparently something in hardware about the new reader interacts with USB port and ClipBrowser that causes the crash.

Sean do post the model number of the Sandisk reader you're having the issue with or confirm that it looks the same as my newer reader (vs the older reader).

The only thing I can think of is that Sandisk did something to an i/o type controller in the newer reader that's causing the issue.

I'm sure I've used this reader before but I think it may have been with the previous version of ClipBrowser otherwise something in a recent Apple software update is involved or at least part of the riddle.

My reader is the SDDR-199-A20. ( SanDisk | ImageMate Multi-Card USB 2.0 | SDDR-199-A20 | B&H ) Both card readers probably share the same controller hardware, which is probably why they both crash the software. I have a feeling it's a bug in the clip browser software that's causing the crash. You're right that it worked fine in previous versions of clip browser.