Solved
"LogMeIn Client" is not optimized for your Mac.
Does logmein not give a crap about their software of the Mac anymore? I've been getting this message for months now.
Forum Discussion
scubadrew I apologize for the G2M mention, I was active in both forums and had my products mixed.
This specific tool is formally known as the Activity Monitor, and here is an overview from Apple: https://support.apple.com/en-us/HT201464
I was wondering if there was anything running there that might be hogging some resources, but you say that you've compared Central with other screen sharing applications, so this may not be relevant.
What kind of delay are you seeing when you click / activate something on an affected host Mac? Are they in different locations / company environments with shared networks?
No problem AshC - I get it :)
Right, I'm not talking about one or a few systems where perhaps they were having some type of resource constraint due to other software running. I'm talking about 50+ systems, in a variety of conditions.
If you read through this (and many other threads) you'll find the MacOS LMI software is woefully out of date. 32 bit applications are about to be completely phased out, yet LMI still runs 32 bit today.
My guess is that MacOS accounts for a small portion of the systems managed and thus few resources are dedicated to improving the Mac software.
Right, I'm not talking about one or a few systems where perhaps they were having some type of resource constraint due to other software running. I'm talking about 50+ systems, in a variety of conditions.
If you read through this (and many other threads) you'll find the MacOS LMI software is woefully out of date. 32 bit applications are about to be completely phased out, yet LMI still runs 32 bit today.
My guess is that MacOS accounts for a small portion of the systems managed and thus few resources are dedicated to improving the Mac software.
I am having this same issue very annoying. As soon as you click off the window logmein crashes. If you minimize before you move around it stays stable. You would think they would have tested the app before the release.
- As previously mentioned, works for a while here but dies eventually.
Work around that's working for me....put your remote session into fullscreen mode. It will stay open as you switch desktops. Hope that helps until support can fix.
With regards to the LMI Pro endpoint crashing, we are currently working to release a fix soon, and will update the community as it completes. Thanks for your patience while we finalize the update.
Beginning to wonder if LMI owes us some credit on service for what amounts to downtime.
Same boat - MacOS10.14 and leave LMI window causes a crash every time.
This is a real pain! Everytime I move off the LogMeIn Client window, the app crashes... This is very frustrating. When will there be an update?
pass me a mail option and I can mail it in...
I apologize if some Macs that have been updated to the newest OS and LMI versions are still encountering issues.
We would very much like to examine the log files from affected Mac Hosts running the newest software versions. If you can call in at your convenience to support, and reference this discussion, we can collect those files and forward them onto engineering to diagnose.
- Honestly, I briefly tested the Mohave Beta when it first released as a public beta and the same issue was present then as well. I am absolutely shocked that they couldn't fix it in the last several months. Such a basic issue which occurs 100% of the time is not excusable for them to overlook.
I have this same issue. Release version of Mohave upgraded this morning. My installed version of Logmein client is 4.1.6927. Any time I click out of the logmein window of a remote host the Logmein application crashes.
Try this. Connect to a remote machine, then expand the remote viewing window to fill your screen. Does that help? I think I did something like and it stopped crashing on me. Or maybe I changed screen color depth?
Yes. Crashes as soon as any other windows is given focus.
ocess: LogMeIn Client [87473]
Path: /Applications/LogMeIn Client.app/Contents/MacOS/LogMeIn Client
Identifier: com.logmein.ignition
Version: 4.1.6927 (4.1.0.6927)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: LogMeIn Client [87473]
User ID: 501Date/Time: 2018-09-25 04:31:24.293 +0200
OS Version: Mac OS X 10.14 (18A389)
Report Version: 12
Bridge OS Version: 3.0 (16P375)
Anonymous UUID: A2C62898-FB58-35F0-BDC5-314A9B739EB9Sleep/Wake UUID: 3A355626-1CDA-4A75-AF00-57608CE676FF
Time Awake Since Boot: 230000 seconds
Time Since Wake: 590 secondsSystem Integrity Protection: enabled
Crashed Thread: 0 TLMIApplicationMain Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_INSTRUCTION (SIGILL)
Exception Codes: 0x0000000000000001, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFYTermination Signal: Illegal instruction: 4
Termination Reason: Namespace SIGNAL, Code 0x4
Terminating Process: exc handler [87473]Application Specific Information:
*** CFRelease() called with NULL ***Thread 0 Crashed:: TLMIApplicationMain Dispatch queue: com.apple.main-thread
0 com.apple.CoreFoundation 0x00007fff2e59e55e CFRelease + 109
1 com.logmein.remctrlplugin 0x0000000114779656 0x11468e000 + 964182
2 com.logmein.remctrlplugin 0x00000001146ad769 0x11468e000 + 128873
3 com.logmein.remctrlplugin 0x00000001146ad5fd 0x11468e000 + 128509
4 com.logmein.remctrlplugin 0x00000001146afc6b 0x11468e000 + 138347
5 com.logmein.remctrlplugin 0x00000001146b14a5 0x11468e000 + 144549
6 com.logmein.remctrlplugin 0x0000000114777d7c 0x11468e000 + 957820
7 com.logmein.remctrlplugin 0x000000011477029a 0x11468e000 + 926362
8 com.apple.AppKit 0x00007fff2bc51205 _NSViewDrawRect + 66
9 com.apple.AppKit 0x00007fff2bc4fabd -[NSView(NSInternal) _recursive:displayRectIgnoringOpacity:inContext:shouldChangeFontReferenceColor:stopAtLayerBackedViews:] + 1545
10 com.apple.AppKit 0x00007fff2bc4f4a2 __46-[NSView(NSLayerKitGlue) drawLayer:inContext:]_block_invoke + 192
11 com.apple.AppKit 0x00007fff2bc4f201 -[NSView(NSLayerKitGlue) _drawViewBackingLayer:inContext:drawingHandler:] + 1769
12 com.apple.QuartzCore 0x00007fff39563aaf CABackingStoreUpdate_ + 577
13 com.apple.QuartzCore 0x00007fff395c5325 invocation function for block in CA::Layer::display_() + 53
14 com.apple.QuartzCore 0x00007fff39562c90 -[CALayer _display] + 1839
15 com.apple.AppKit 0x00007fff2bc4e75a _NSBackingLayerDisplay + 531
16 com.apple.AppKit 0x00007fff2bc32cc9 -[_NSViewBackingLayer display] + 811
17 com.apple.QuartzCore 0x00007fff395621bc CA::Layer::display_if_needed(CA::Transaction*) + 634
18 com.apple.QuartzCore 0x00007fff39550447 CA::Context::commit_transaction(CA::Transaction*) + 319
19 com.apple.QuartzCore 0x00007fff3954fd20 CA::Transaction::commit() + 576
20 com.apple.AppKit 0x00007fff2bc298f5 __65+[CATransaction(NSCATransaction) NS_setFlushesWithDisplayRefresh]_block_invoke + 274
21 com.apple.CoreFoundation 0x00007fff2e62d95d __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 23
22 com.apple.CoreFoundation 0x00007fff2e62d892 __CFRunLoopDoObservers + 452
23 com.apple.CoreFoundation 0x00007fff2e5cf3c5 __CFRunLoopRun + 1166
24 com.apple.CoreFoundation 0x00007fff2e5cece4 CFRunLoopRunSpecific + 463
25 com.apple.HIToolbox 0x00007fff2d868895 RunCurrentEventLoopInMode + 293
26 com.apple.HIToolbox 0x00007fff2d8684d4 ReceiveNextEventCommon + 371
27 com.apple.HIToolbox 0x00007fff2d868348 _BlockUntilNextEventMatchingListInModeWithFilter + 64
28 com.apple.AppKit 0x00007fff2bb2595b _DPSNextEvent + 997
29 com.apple.AppKit 0x00007fff2bb246fa -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1362
30 com.apple.AppKit 0x00007fff2bb1e75d -[NSApplication run] + 699
31 com.apple.AppKit 0x00007fff2bb0de97 NSApplicationMain + 780
32 LogMeIn Client 0x0000000107b57864 0x107b4b000 + 51300
33 libdyld.dylib 0x00007fff5b668085 start + 1Version 4.1.6927 (PlugIn: 1.0.1948) crashes every single time I switch screens.
Its absolutely ridiculous that the client has been crashes since the first Mojave build and LMI has done nothing to address the problem. And they won't have this fixed for a month?? I can't believe I pay for this app!
Are you on LogMeIn Version 4.1.6927 (PlugIn: 1.0.1948)?
I'm running it on macOS 10.14 (18A389) and it's mostly stable.
I'm still looking forward to the upgrade next month, hopefully it's more efficient with resources.
I am on the release from the 19th and logmein crashes 100% of the time I make anything else the active application. Even if I don't it still crashes randomly.
Other than the application being 32 bit I havent had major issues for about a month or two. Just minor things here and there which I can live with until the update comes out next month.
Hi,
If you are still experiencing issues, can you please confirm if you have updated to our September 19th release?
I've asked end-users not to install Mojave until things shake out. I've suggested months. But that will not stop a few from just doing it.
So come Sept 24 there will be a raft of calls, texts, and emails.It's no stable, we are expecting major issues with all of our Mac clients who have LogMeIn and install Mojave.
Thanks for early warning about bugginess.
They've had six months to get ready for the rollout but it will be released one month late.
My concern is twofold:
- What will I see on my end
- What other users will do with Mojave before consulting with meAnd companies like LMI should be running these betas to develop new software for us - something they NEVER DO. I am sick and tired of their BS frankly.
