ShowURL crash

Hello,

I’ve got a button which does a bit of stuff and then uses ShowURL. On one of our customers’ machines, I get a hard crash (not an exception). The stack finishes:

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 ??? 0xff00d000 0 + 4278243328 1 com.xojo.XojoFramework 0x03016e88 0x2f6d000 + 695944 2 com.xojo.XojoFramework 0x03016da7 GlobalShowURL + 43 3 com.lightbluesoftware.lightblue 0x001f4298 REALbasic.ShowURL%%s + 34

He also seems to be getting one when opening a file we downloaded:

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 ??? 0xff00c000 0 + 4278239232 1 com.xojo.XojoFramework 0x0307f43f FolderItemLaunch + 161 2 com.lightbluesoftware.lightblue 0x000a4671 FolderItem.Launch%%o<FolderItem>b + 51 3 com.lightbluesoftware.lightblue 0x00f194f6 fileFunctions.openFile%b%o<FolderItem> + 3710

Does anyone have any bright ideas as to what could be going on here?

Best wishes,

Hamish

Can you post the crash logs somewhere?

Sure, there’s one at https://dl.dropboxusercontent.com/u/15108631/crash1.txt

That’s very strange. Both crashes are places we call into LaunchServices to open a URL, but I don’t see anything wrong with the code.

Yep, it works happily on others’ computers; it seems to crash just on his, and it’s only recently started happening. Any way of reinstalling LaunchServices or otherwise making his computer happier?

You can open the url from a shell :

dim s as new shell s.Execute("open http://xojo.com")

I suppose I could, but I’d rather get it working if it should work!

When a crash occurs on only ONE customer’s machine, I would be inclined to blame his system…

Difficult to fix code when it is executing in a minefield.

I agree. But he is our customer, and he is inclined to blame us, whatever his system settings.

Might be worth having the customer try creating a new user account and trying the app from there to see if they still get the crash.

Unfortunately, I’m not sure how you’d rebuild launch services if it is at fault. Google searches find some commands, but they don’t seem to be compatible with El Cap.

Hi Hamish, something changed on the user’s machine since it used to work, so what was it? Power cut? Software update? Disk issue? I have occasionally found a bad or badly connected cable or malfunctioning peripheral can cause weird issues. Also do a Verify Disk, and a Repair Disk Permissions can fix oddities.

All customers will blame you, even if it’s a bug in the OS.

I would clear his browser internet cache.

If that was on PC, I would blame the antivirus. That is the kind of thing they do. But by the same token, worms and viruses can also do this kind of stuff.

Since it manifests on one user machine only, why not apply the workaround for his sole machine ? Should be possible to apply with a switch setting somewhere.

We all have at one point to put limits, let alone with supported systems.

what is the exact url he receives? it seems some xcode developers had the same trouble. It could happen if the url is inclomple. (missing file:// or http:// or the wrong sequence).

At which point that’s an Apple bug, as it should fail gracefully.

Which Sam already noted

Back in 2013 there was report of “File:///” crashing most browsers. But that has been patched since. However, if the customer is still using an old system or an old version of Safari. It could be of the same nature.

http://thenextweb.com/shareables/2013/02/02/typing-these-eight-characters-will-crash-almost-any-application-on-your-mac/

[quote=251318:@Michel Bujardet]Back in 2013 there was report of “File:///” crashing most browsers. But that has been patched since. However, if the customer is still using an old system or an old version of Safari. It could be of the same nature.

http://thenextweb.com/shareables/2013/02/02/typing-these-eight-characters-will-crash-almost-any-application-on-your-mac/[/quote]
I think this is the problem, perhaps the user hasn’t updated since or so.