TLDR; creating or editing auto typing macro has caused a kernel panic on my Mac three separate times now. The first time was inadvertent. The second and third times were me just trying to reproduce this issue before creating this bug report.
——————————
I tried creating an RDP Auto Typing Macro (After Connection) and as soon as I started typing in one of the fields, my computer froze and crashed. It went to a black screen and then said that my Mac had rebooted unexpectedly.
After booting back up, I attempted it again and the kernel panicked again. Just to be certain, I tried one more time. This time I got a little bit further in that it let me create the event rule. But before I saved it, I switched over to the Before Connection tab and then back to After Connection. When I tried to edit any field, the kernel panicked again and rebooted. I'm going to paste the MacOS kernel panic problem report details in case they help.MacBook Pro (Retina, 15-inch, Mid 2015)macOS Catalina 10.15.1RDM Free Edition 2020.1.2.0
——————————panic(cpu 6 caller 0xffffff801e062e0a): Kernel trap at 0xffffff7fa14c634e, type 6=invalid opcode, registers:CR0: 0x000000008001003b, CR2: 0x000070000959ed54, CR3: 0x000000046a4f406a, CR4: 0x00000000001626e0RAX: 0x0000000000000000, RBX: 0x0000000000000000, RCX: 0x0000000000000000, RDX: 0xffffff9232122ff0RSP: 0xffffff9232123160, RBP: 0xffffff9232123160, RSI: 0x0000000000000503, RDI: 0xffffff8041442a00R8: 0x0000000000000000, R9: 0x0000000000989680, R10: 0x0000000000000000, R11: 0x0000000000000005R12: 0x0000000000000004, R13: 0xffffff8043684670, R14: 0xffffff9232123180, R15: 0xffffff8043684670RFL: 0x0000000000010286, RIP: 0xffffff7fa14c634e, CS: 0x0000000000000008, SS: 0x0000000000000000Fault CR2: 0x000070000959ed54, Error code: 0x0000000000000000, Fault CPU: 0x6, PL: 0, VF: 0Backtrace (CPU 6), Frame : Return Address0xffffff9232122bc0 : 0xffffff801df39a3b 0xffffff9232122c10 : 0xffffff801e070fe5 0xffffff9232122c50 : 0xffffff801e062a5e 0xffffff9232122ca0 : 0xffffff801dee0a40 0xffffff9232122cc0 : 0xffffff801df39127 0xffffff9232122dc0 : 0xffffff801df3950b 0xffffff9232122e10 : 0xffffff801e6d17f9 0xffffff9232122e80 : 0xffffff801e062e0a 0xffffff9232123000 : 0xffffff801e062b08 0xffffff9232123050 : 0xffffff801dee0a40 0xffffff9232123070 : 0xffffff7fa14c634e 0xffffff9232123160 : 0xffffff7fa1426490 0xffffff92321231a0 : 0xffffff7fa1434655 0xffffff92321231f0 : 0xffffff7fa13bd6db 0xffffff9232123260 : 0xffffff7f9f3cb966 0xffffff92321232b0 : 0xffffff7f9f3d9438 0xffffff92321232f0 : 0xffffff7f9f3d933b 0xffffff9232123320 : 0xffffff7f9f3f5bb0 0xffffff9232123390 : 0xffffff7fa13c309a 0xffffff92321233c0 : 0xffffff7fa13e73f9 0xffffff9232123400 : 0xffffff7fa13e76bf 0xffffff9232123430 : 0xffffff7fa13e50f4 0xffffff9232123450 : 0xffffff7fa13c5fa2 0xffffff9232123510 : 0xffffff7f9f3eabca 0xffffff9232123590 : 0xffffff7f9f3ea61f 0xffffff92321235b0 : 0xffffff7f9f3ecc5c 0xffffff92321235f0 : 0xffffff7fa13c9c43 0xffffff9232123610 : 0xffffff7fa13c8588 0xffffff92321236b0 : 0xffffff7f9f40a768 0xffffff92321236f0 : 0xffffff7f9f40aab1 0xffffff9232123990 : 0xffffff7f9f40bbfe 0xffffff9232123a20 : 0xffffff7f9f409d80 0xffffff9232123a80 : 0xffffff7f9f409b6d 0xffffff9232123ad0 : 0xffffff7f9f408bb7 0xffffff9232123b10 : 0xffffff801e6663fb 0xffffff9232123b60 : 0xffffff801e66f393 0xffffff9232123ca0 : 0xffffff801e020b92 0xffffff9232123db0 : 0xffffff801df3f8b8 0xffffff9232123e10 : 0xffffff801df16545 0xffffff9232123e70 : 0xffffff801df2cff5 0xffffff9232123f00 : 0xffffff801e049085 0xffffff9232123fa0 : 0xffffff801dee1226 Kernel Extensions in backtrace: com.apple.iokit.IOAcceleratorFamily2(438.2.7)[72B8A0B5-E12C-3764-9187-0AC0E93416F9]@0xffffff7f9f3c7000->0xffffff7f9f48afff dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[180FC5AB-0E47-35BC-91DF-609EBE8ED4A5]@0xffffff7f9f1ff000 dependency: com.apple.iokit.IOPCIFamily(2.9)[AA7C7A4F-9F5D-3533-9E78-177C3B6A72BF]@0xffffff7f9e940000 dependency: com.apple.iokit.IOSurface(269.6)[39DC4195-B168-3895-ACD5-E731581855F8]@0xffffff7f9f337000 dependency: com.apple.iokit.IOGraphicsFamily(568)[247C211E-C250-351C-BCE2-4DB9D3003E10]@0xffffff7f9f368000 dependency: com.apple.iokit.IOReportFamily(47)[2CCA7DD3-C33F-3CA4-A213-BC83D3D997B0]@0xffffff7f9ef36000 com.apple.kext.AMDRadeonX4000(3.0.2)[1E092428-A3E6-3063-B692-B943B1565B91]@0xffffff7fa13b4000->0xffffff7fa17f9fff dependency: com.apple.iokit.IOPCIFamily(2.9)[AA7C7A4F-9F5D-3533-9E78-177C3B6A72BF]@0xffffff7f9e940000 dependency: com.apple.iokit.IOSurface(269.6)[39DC4195-B168-3895-ACD5-E731581855F8]@0xffffff7f9f337000 dependency: com.apple.iokit.IOGraphicsFamily(568)[247C211E-C250-351C-BCE2-4DB9D3003E10]@0xffffff7f9f368000 dependency: com.apple.iokit.IOAcceleratorFamily2(438.2.7)[72B8A0B5-E12C-3764-9187-0AC0E93416F9]@0xffffff7f9f3c7000BSD process name corresponding to current thread: WindowServerMac OS version:19B88Kernel version:Darwin Kernel Version 19.0.0: Thu Oct 17 16:17:15 PDT 2019; root:xnu-6153.41.3~29/RELEASE_X86_64Kernel UUID: 7503CD47-851F-321E-8747-50DB4299165FKernel slide: 0x000000001dc00000Kernel text base: 0xffffff801de00000__HIB text base: 0xffffff801dd00000System model name: MacBookPro11,5 (Mac-06F11F11946D27C5)System shutdown begun: NOPanic diags file available: YES (0x0)System uptime in nanoseconds: 1298021777746last loaded kext at 257004068177: @filesystems.msdosfs 1.10 (addr 0xffffff7f9f637000, size 69632)last unloaded kext at 446574159253: >usb.!UHostPacketFilter 1.0 (addr 0xffffff7f9f90a000, size 24576)loaded kexts:com.github.kbfuse.filesystems.kbfuse 3.10.0com.paloaltonetworks.kext.pangpd 1.0.0com.sophos.kext.oas 9.9.4com.sophos.kext.sfm 9.9.4com.sophos.nke.swi 9.9.4org.pqrs.driver.Karabiner.VirtualHIDDevice.v061000 6.10.0com.intel.kext.intelhaxm 6.2.1com.asix.driver.ax88179-178a 1.12.0com.sophos.driver.devctrl 9.9.4@filesystems.smbfs 3.4@fileutil 20.036.15@filesystems.autofs 3.0>!AHDA 283.14>AGPM 111.2.5>!APlatformEnabler 2.7.0d0>X86PlatformShim 1.0.0>!AUpstreamUserClient 3.6.8@kext.AMDFramebuffer 3.0.2@kext.AMDRadeonX4000 3.0.2@kext.AMDRadeonServiceManager 3.0.2>!AGraphicsDevicePolicy 4.5.9@AGDCPluginDisplayMetrics 4.5.9>!AHV 1|IOUserEthernet 1.0.1>!A!IHD5000Graphics 14.0.2|IO!BSerialManager 7.0.1f1>pmtelemetry 1>!ACameraInterface 7.6.0@Dont_Steal_Mac_OS_X 7.0.0|Broadcom!B20703USBTransport 7.0.1f1>!A!ISlowAdaptiveClocking 4.0.0>AGDCBacklightControl 4.5.9@kext.AMD7000!C 3.0.2>eficheck 1>!A!IFramebufferAzul 14.0.2>!ALPC 3.1>!AMuxControl 4.5.9>!AMCCSControl 1.13>!ASMCLMU 212>AudioAUUC 1.70>!AThunderboltIP 3.1.3>!ATopCaseHIDEventDriver 3410.1>!UTopCaseDriver 3410.1>!UCardReader 489.41.1@filesystems.apfs 1412.41.1>AirPort.BrcmNIC 1400.1.1>!AAHCIPort 341.0.2>!AVirtIO 1.0@filesystems.hfs.kext 522.0.9@!AFSCompression.!AFSCompressionTypeDataless 1.0.0d1@BootCache 40@!AFSCompression.!AFSCompressionTypeZlib 1.0.0@private.KextAudit 1.0>!ASmartBatteryManager 161.0.0>!AACPIButtons 6.1>!AHPET 1.8>!ARTC 2.0>!ASMBIOS 2.1>!AACPIEC 6.1>!AAPIC 1.7$!AImage4 1@nke.applicationfirewall 303$TMSafetyNet 8@!ASystemPolicy 2.0.0|EndpointSecurity 1@kext.triggers 1.0>DspFuncLib 283.14@kext.OSvKernDSPLib 529@kext.AMDRadeonX4030HWLibs 1.0@kext.AMDRadeonX4000HWServices 3.0.2|IOAVB!F 800.17>!ASSE 1.0|Broadcom!BHost!CUSBTransport 7.0.1f1|IO!BHost!CUSBTransport 7.0.1f1|IO!BHost!CTransport 7.0.1f1@!AGPUWrangler 4.5.9|IOSlowAdaptiveClocking!F 1.0.0@kext.AMDSupport 3.0.2>X86PlatformPlugin 1.0.0|IOAccelerator!F2 438.2.7>IOPlatformPlugin!F 6.0.0d8>!ABacklightExpert 1.1.0|IONDRVSupport 568@!AGraphicsDeviceControl 4.5.9>!AGraphicsControl 4.5.9>!AHDA!C 283.14|IOHDA!F 283.14>!ASMBus!C 1.0.18d1|IOGraphics!F 568@plugin.IOgPTPPlugin 810.1|IOEthernetAVB!C 1.1.0>!AActuatorDriver 3410.2>!AHS!BDriver 3410.1>IO!BHIDDriver 7.0.1f1|IO!B!F 7.0.1f1|IO!BPacketLogger 7.0.1f1>!AMultitouchDriver 3410.2>!AInputDeviceSupport 3410.1>!AHIDKeyboard 209>usb.IOUSBHostHIDDevice 1.2>!UAudio 320.49|IOAudio!F 300.2@vecLib.kext 1.2.0>usb.!UHub 1.2>usb.networking 5.0.0>usb.!UHostCompositeDevice 1.2|IOAHCIBlock!S 316.40.3|IO80211!F 1200.12.2b1>mDNSOffloadUserClient 1.0.1b8>corecapture 1.0.4|IOSkywalk!F 1>usb.!UXHCIPCI 1.2>usb.!UXHCI 1.2|IOAHCI!F 290.0.1|IOSerial!F 11|IOSurface 269.6@filesystems.hfs.encodings.kext 1>!AThunderboltPCIDownAdapter 2.5.2>!AThunderboltDPInAdapter 6.2.3>!AThunderboltDPAdapter!F 6.2.3>!AThunderboltNHI 5.8.0|IOThunderbolt!F 7.4.6|IOUSB!F 900.4.2>!AEFINVRAM 2.1>!AEFIRuntime 2.1|IOSMBus!F 1.1|IOHID!F 2.0.0$quarantine 4$sandbox 300.0@kext.!AMatch 1.0.0d1>DiskImages 493.0.0>!AFDEKeyStore 28.30>!AEffaceable!S 1.0>!AKeyStore 2>!UTDM 489.41.1|IOSCSIBlockCommandsDevice 422.0.2>!ACredentialManager 1.0>KernelRelayHost 1>!ASEPManager 1.0.1>IOSlaveProcessor 1|IOUSBMass!SDriver 157.40.7|IOSCSIArchitectureModel!F 422.0.2|IOUSBHost!F 1.2>!UHostMergeProperties 1.2>usb.!UCommon 1.0>!ABusPower!C 1.0|CoreAnalytics!F 1>!AMobileFileIntegrity 1.0.5@kext.CoreTrust 1|IOTimeSync!F 810.1|IONetworking!F 3.4|IOReport!F 47|IO!S!F 2.1>!AACPIPlatform 6.1>!ASMC 3.1.9>watchdog 1|IOPCI!F 2.9|IOACPI!F 1.4@kec.pthread 1@kec.corecrypto 1.0@kec.Libm 1
Let me know if you want me to provide any RDM-specific logs. I did try looking at the logs found in Menubar > Help > Application Logs but they didn't seem to show anything relevant.
Hi Blake,
Can you get me a screenshot of the exact view you were trying to fill? Could you highlight in this screenshot the field you were trying to edit? When relaunching RDM afterwards was it prompting you with any error window?
Best regards,
Xavier Fortin
RDM did prompt me with an error window, but I don't recall what the error said, but it seemed totally irrelevant.
It didn't seem to be consistent. On the three separate crashes, it happened in a few different fields. In the case of the third crash, I was able to edit all of them, change to a different tab, then come back and try changing some of the values and that's when it crashed on me.
rdm1.png
Hi Blake,
And this only ever happened in this specific view? I've been unable to reproduce so far.
I did indeed receive your crash report and you are right, there is nothing really indicative of the issue. In fact, to the eye, it looks like a simple force quit of the app. So, for all that we know, the crash is pretty much only on the macOS side. Ultimately, I'd try updating macOS and see if the problem still occurs. There is honestly not much that we are doing in this window that would justify such a strong response from the OS.
Best regards,
Xavier Fortin