LinkLiar crash almost immediately

Question

LinkLiar crash almost immediately

michaelstepner opened this issue 9 years ago · comments

I just installed LinkLiar (OS X Yosemite, 10.10.5) and it hangs then crashes almost immediately after I click on its menu bar icon to interact with it. I've turned on debug mode, and would be happy to send logs if you guide me on what to send.

halo · Answer 1 · Sat Jan 23 2016 04:10:18 GMT+0800 (China Standard Time)

Hm, sorry to hear you have trouble running it. It works fine for me on 10.10.5.

Do you have any (additional) network interfaces attached to your mac? Even a bluetooth dongle?
In System Preferences -> Security -> General -> Allow apps downloaded from... what setting do you have there?
Where is the application file located when you run it?
If you have the logs (run the Console.app to see them), the last one or two lines before the crash would be helpful. So I can get a hint as to where in the code it dies.

If you run ifconfig | grep flags in a Terminal and look at the first thing in every row, I have these:

"lo0, gif0, stf0, en0, en1, p2p0, awdsl0, bridge0, utun0"

Do you have anthing in your list apart from those I have?

EDIT: I'm in another time zone, will get back to you in like 12 hrs :)

Michael Stepner · Answer 2 · Sat Jan 23 2016 04:29:54 GMT+0800 (China Standard Time)

Hi halo,

Do you have any (additional) network interfaces attached to your mac? Even a bluetooth dongle?
- Under System Preferences > Network, I have the following. Nothing but wifi is attached.
In System Preferences -> Security -> General -> Allow apps downloaded from... what setting do you have there?
- "Allow apps downloaded from Mac App Store and identified developers." I launch other apps such as LinkLiar by holding control while clicking on them the first time, which prompts me whether to authorize them. Subsequent launches do not cause a prompt.
Where is the application file located when you run it?
- I dropped it in my Applications folder
If you have the logs (run the Console.app to see them), the last one or two lines before the crash would be helpful. So I can get a hint as to where in the code it dies.
- I've included all the items that occurred between me clicking on the menu bar icon and it crashing.

2016-01-22 3:26:40.978 PM Link[23246]: Refreshing menu before opening it...
2016-01-22 3:26:40.979 PM Link[23246]: Going to refresh...
2016-01-22 3:26:41.005 PM Link[23246]: Proxying from Synchronizer to Intercom...
2016-01-22 3:26:41.006 PM Link[23246]: Intercom is going to check HelperTool version...
2016-01-22 3:26:41.006 PM Link[23246]: connectAndExecuteCommandBlock
2016-01-22 3:26:41.006 PM Link[23246]: Connecting to Helper Tool...
2016-01-22 3:26:41.006 PM Link[23246]: running command...
2016-01-22 3:26:41.006 PM Link[23246]: Yeah, this is the Helper I want.
2016-01-22 3:26:41.014 PM Link[23246]: Don't know what to do with hardware MAC aa:bb:cc:dd:ee:ff of Wi-Fi ∙ en0
2016-01-22 3:26:41.014 PM Link[23246]: Don't know what to do with hardware MAC aa:bb:cc:dd:ee:ff of Wi-Fi ∙ en0
2016-01-22 3:26:41.014 PM Link[23246]: Don't know what to do with hardware MAC aa:bb:cc:dd:ee:ff of Wi-Fi ∙ en0
2016-01-22 3:26:41.014 PM Link[23246]: Don't know what to do with hardware MAC aa:bb:cc:dd:ee:ff of Wi-Fi ∙ en0
2016-01-22 3:26:48.386 PM Link[23246]: Refreshing menu before opening it...
2016-01-22 3:26:48.386 PM Link[23246]: Going to refresh...
2016-01-22 3:26:57.993 PM Link[23246]: CoreAnimation: warning, deleted thread with uncommitted CATransaction; set CA_DEBUG_TRANSACTIONS=1 in environment to log backtraces.
2016-01-22 3:27:09.511 PM Link[23246]: Proxying from Synchronizer to Intercom...
2016-01-22 3:27:09.511 PM Link[23246]: Intercom is going to check HelperTool version...
2016-01-22 3:27:09.511 PM Link[23246]: connectAndExecuteCommandBlock
2016-01-22 3:27:09.511 PM Link[23246]: Connecting to Helper Tool...
2016-01-22 3:27:09.511 PM Link[23246]: running command...
2016-01-22 3:27:09.512 PM Link[23246]: Yeah, this is the Helper I want.
2016-01-22 3:27:09.521 PM Link[23246]: Don't know what to do with hardware MAC aa:bb:cc:dd:ee:ff of Wi-Fi ∙ en0
2016-01-22 3:27:09.521 PM Link[23246]: Don't know what to do with hardware MAC aa:bb:cc:dd:ee:ff of Wi-Fi ∙ en0
2016-01-22 3:27:09.521 PM Link[23246]: Don't know what to do with hardware MAC aa:bb:cc:dd:ee:ff of Wi-Fi ∙ en0
2016-01-22 3:27:09.521 PM Link[23246]: Don't know what to do with hardware MAC aa:bb:cc:dd:ee:ff of Wi-Fi ∙ en0
2016-01-22 3:27:09.605 PM com.apple.xpc.launchd[1]: (com.apple.ReportCrash[23281]) Endpoint has been activated through legacy launch(3) APIs. Please switch to XPC or bootstrap_check_in(): com.apple.ReportCrash
2016-01-22 3:27:10.094 PM com.apple.xpc.launchd[1]: (com.funkensturm.Link.212748[23246]) Service exited due to signal: Segmentation fault: 11
2016-01-22 3:27:10.139 PM ReportCrash[23281]: Saved crash report for Link[23246] version 1.0 (1.1.2) to /Users/michael/Library/Logs/DiagnosticReports/Link_2016-01-22-152710_Planarian-4.crash

Michael Stepner · Answer 3 · Sat Jan 23 2016 04:34:01 GMT+0800 (China Standard Time)

Oops, missed one:

If you run ifconfig | grep flags in a Terminal and look at the first thing in every row, I have these: lo0, gif0, stf0, en0, en1, p2p0, awdsl0, bridge0, utun0. Do you have anthing in your list apart from those I have?
- I've got lo0, gif0, stf0, en0, en1, en2, bridge0, p2p0, awdl0, utun0. The only difference appears to be en2.

halo · Answer 4 · Sat Jan 23 2016 05:18:23 GMT+0800 (China Standard Time)

Ok, nothing weird so far.

iPad and iPhone not connected, right?
I think en2 is suspicious yes. Do you have a Macbook with a FireWire port? If no other device is attached (e.g. via USB), you should not have more than two interfaces on newer laptops.
In your Network System Preferences in the top where it says "Location" you could try to create a fresh new Location without any interfaces (or maybe just WiFi). You'll loose your Internet Connection when you change to that location, but I suppose LinkLiar would not crash.
I don't exactly follow at which point it crashes: Did you manage to authorizes the Helper Tool? Form the logs I gather that you succeeded with that. I mean what do you see at all in the LinkLiar Menu Item List before it crashes?
In the last line of your log, there is a crash report saved to your disk. Could you email me that to crashes@posteo.ee or simply post it here if there is no sensitive info in it?

PS: I recommend you always redact your MAC address when posting logs. I did that for you now by editing your post. Also there were some IP addresses in the log i removed.

More debugging tomorrow ;) Thank you for helping to debug!

halo · Answer 5 · Sat Feb 06 2016 04:03:53 GMT+0800 (China Standard Time)

Hi, sorry I don't feel I have much to reproduce the issue. Apart from the questions in my previous comment, the only thing I could imagine that's really different on your system is is trying to allow apps in your security settings and see if it works any better.

Michael Stepner · Answer 6 · Fri May 13 2016 00:59:52 GMT+0800 (China Standard Time)

Hello, I just decided to revisit this and see if I could get to the bottom the issue. Except, I can no longer reproduce the bug! LinkLiar seems to be working properly on my machine now: it doesn't crash, and I can successfully get it to change my MAC.

My system has changed slightly since we last spoke (ex: I'm now running OS X El Capitan 10.11.4), but it's still the same hardware and mostly the same configuration. I'm not sure what was causing that bug in January... sorry I couldn't be more of a help tracking it down!

halo · Answer 7 · Fri May 13 2016 01:18:39 GMT+0800 (China Standard Time)

No worries, I'm glad it's working for you. I'm aware of being able to crash LinkLiar by clicking pretty fast back and forth in the menu when the devices change, but it doesn't happen often.

Thanks for reporting!