[MAC] Universal Autofill instantly crashes 1PW
Tried to use Universal Autofill for the first time when logging into view my account information in the Mac AppStore app, and I type cmd-\ and the window pop ups with matching logins, but when I press Return to Autofill, 1Password just crashes instantly, everytime.
Here's an excerpt from the 1Password quit unexpectedly window:
Process: 1Password [70124] Path: /Applications/1Password.app/Contents/MacOS/1Password Identifier: com.1password.1password Version: 8.8.0-8.NIGHTLY (8.8.0-8.NIGHTLY.110944) Code Type: X86-64 (Native) Parent Process: ??? [1] Responsible: 1Password [70124] User ID: 501 Date/Time: 2022-05-03 22:16:11.696 +0100 OS Version: Mac OS X 10.15.7 (19H1824) Report Version: 12 Anonymous UUID: 5BCC78F0-2EDC-664C-D0D9-D006E2AFAE57 Sleep/Wake UUID: C298E06E-B186-49A1-91B2-A90B55FF9D88 Time Awake Since Boot: 220000 seconds Time Since Wake: 56000 seconds System Integrity Protection: enabled Crashed Thread: 50 tokio-runtime-worker Exception Type: EXC_BAD_INSTRUCTION (SIGILL) Exception Codes: 0x0000000000000001, 0x0000000000000000 Exception Note: EXC_CORPSE_NOTIFY Termination Signal: Illegal instruction: 4 Termination Reason: Namespace SIGNAL, Code 0x4 Terminating Process: exc handler [70124] Application Specific Information: BUG IN CLIENT OF LIBDISPATCH: Assertion failed: Block was expected to execute on queue [com.apple.main-thread]
I can copy and paste the password ok, but not autofill it.
1Password Version: 8.8.0-8.NIGHTLY
Extension Version: Not Provided
OS Version: macOS 10.15.7
Comments
-
A bit of additional info... I just tried switching to the Production version (v8.7.0 Build 80700098), just to check if it was something introduced in the Nightly versions, but unfortunately, it still does the same... Crashes instantly on attempting to Autofill,
I can't be the only one running Catalina am I - although I haven't seen any other reports of this?
0 -
Thanks! I was wondering… It has to be something different then :-) (which is sad, since the more people are affected by the same bug, the more likely it is that it will be identified and corrected — my crashing issue has been going on for quite some time and making my life miserable).
I haven’t seen any Universal Autofill on my Catalina Mac, but it’s not a feature I use often. I’ll try to play with it some more to see whether it could indeed be a Catalina issue.
Corentin
0 -
We've had two more reports of a crash when using Universal Autofill on Catalina. @snozdop if you could provide a stack trace, that would help us dig in faster. I think that should have been displayed in the same "1Password quit unexpectedly" window that you copied from before. Could you send us the entire contents of that window? If you want to email it instead of posting here, just send to support+forum@1password.com and include a link to this discussion.
Thanks!
0 -
@rob I've sent the full crash report via email and here's the support ID: [#RHJ-94613-793]
I don't know whether it is related at all, but during beta testing there was another seemingly Catalina-specific crashing bug when updating the app which was subsequently fixed. Maybe worth a look to see if it's a similar Catalina-only issue.
0 -
👍
0 -
I installed 1Password 8 last night on two of my machines, upgrading from 1Password 7. The Monterey install is functioning just fine with CMD-Shift-Space and CMD-.
However, on my Catalina machine, it’s either crashing or locking the vault every single time I invoke auto fill with both CMD-Shift-Space and CMD-. So it’s pretty much unusable at this time as I would need to manually copy and paste my logins.
Let me know if you need any logs or reports.
0 -
I'm having the same issue on Big Sur. I sent you my crash report.
Support ID: [#CGQ-68159-525]0 -
Same here on 10.15.7 (iMac) #KSN-25819-394
0 -
Running into the same issue on my MacBook Air M1 running Big Sur. I installed 1password8 for mac, verified that the browser extensions work and then tried universal autofill on a desktop mac app. Reproduced this several times on the same app. pasting the log below
Process: 1Password [58051] Path: /Applications/1Password.app/Contents/MacOS/1Password Identifier: com.1password.1password Version: 8.7.0 (8.7.0.109983) Code Type: ARM-64 (Native) Parent Process: ??? [1] Responsible: 1Password [58051] User ID: 501 Date/Time: 2022-05-09 16:19:40.087 -0400 OS Version: macOS 11.0 (20A2411) Report Version: 12 Anonymous UUID: 97AD6C78-6BE3-4BEF-AA55-0A4EBB419773 Sleep/Wake UUID: 2F3FE727-1023-4440-B1E4-1F215FC7C708 Time Awake Since Boot: 210000 seconds Time Since Wake: 12000 seconds System Integrity Protection: enabled Crashed Thread: 49 tokio-runtime-worker Exception Type: EXC_BREAKPOINT (SIGTRAP) Exception Codes: EXC_ARM_BREAKPOINT at 0x0000000195e1e82c (brk 1) Exception Note: EXC_CORPSE_NOTIFY Termination Signal: Trace/BPT trap: 5 Termination Reason: Namespace SIGNAL, Code 0x5 Terminating Process: exc handler [58051] Application Specific Information: BUG IN CLIENT OF LIBDISPATCH: Assertion failed: Block was expected to execute on queue [com.apple.main-thread] Thread 0:: CrBrowserMain Dispatch queue: com.apple.main-thread 0 libsystem_kernel.dylib 0x0000000195f8fda8 mach_msg_trap + 8 1 libsystem_kernel.dylib 0x0000000195f90158 mach_msg + 76 2 com.apple.CoreFoundation 0x00000001960c3e88 __CFRunLoopServiceMachPort + 380 3 com.apple.CoreFoundation 0x00000001960c235c __CFRunLoopRun + 1216 4 com.apple.CoreFoundation 0x00000001960c1730 CFRunLoopRunSpecific + 600 5 com.apple.HIToolbox 0x000000019dbc8fd4 RunCurrentEventLoopInMode + 292 6 com.apple.HIToolbox 0x000000019dbc8e04 ReceiveNextEventCommon + 688 7 com.apple.HIToolbox 0x000000019dbc8b34 _BlockUntilNextEventMatchingListInModeWithFilter + 76 8 com.apple.AppKit 0x0000000198895ce0 _DPSNextEvent + 868 9 com.apple.AppKit 0x0000000198894660 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1312 10 com.apple.AppKit 0x00000001988864bc -[NSApplication run] + 600 11 com.github.Electron.framework 0x0000000107412700 node::GetEnvironmentIsolateData(node::Environment*) + 9350648 12 com.github.Electron.framework 0x0000000107411008 node::GetEnvironmentIsolateData(node::Environment*) + 9344768 13 com.github.Electron.framework 0x00000001073d8080 node::GetEnvironmentIsolateData(node::Environment*) + 9111416 14 com.github.Electron.framework 0x00000001073a77b4 node::GetEnvironmentIsolateData(node::Environment*) + 8912556 15 com.github.Electron.framework 0x00000001067e887c v8::internal::SetupIsolateDelegate::SetupHeap(v8::internal::Heap*) + 4633896 16 com.github.Electron.framework 0x00000001067ea084 v8::internal::SetupIsolateDelegate::SetupHeap(v8::internal::Heap*) + 4640048 17 com.github.Electron.framework 0x00000001067e6444 v8::internal::SetupIsolateDelegate::SetupHeap(v8::internal::Heap*) + 4624624 18 com.github.Electron.framework 0x0000000104e0ee20 v8::internal::ExternalReference::fast_c_call_caller_pc_address(v8::internal::Isolate*) + 1936 19 com.github.Electron.framework 0x0000000104e0ff9c v8::internal::ExternalReference::fast_c_call_caller_pc_address(v8::internal::Isolate*) + 6412 20 com.github.Electron.framework 0x0000000104e0fa78 v8::internal::ExternalReference::fast_c_call_caller_pc_address(v8::internal::Isolate*) + 5096 21 com.github.Electron.framework 0x0000000104e0e044 v8::internal::compiler::BasicBlock::set_loop_header(v8::internal::compiler::BasicBlock*) + 10812 22 com.github.Electron.framework 0x0000000104e0e978 v8::internal::ExternalReference::fast_c_call_caller_pc_address(v8::internal::Isolate*) + 744 23 com.github.Electron.framework 0x0000000104b8c818 ElectronMain + 128 24 libdyld.dylib 0x0000000195fe4f64 start +
0 -
I upgraded to Monterey from Big Sur and no longer run into the issue.
0 -
Same thing here. I have two older Mac that cannot be upgraded. Newer Mac are fine :-\
Corentin
0 -
Hi folks, thank you for letting us know your current state of functionality with this. We're actively working on the issue and will look forward to sharing more when we're able to.
0 -
On a quick initial test, it looks like today's NIGHTLY release (80800098) has fixed this issue. I was able to use universal autofill to fill my Mac AppStore password.
Yay!
0 -
Same issue on Catalina using the latest 1Password as of today: 80700098 ("PRODUCTION channel").
I also can't upgrade to Monterey so it'd be great to see the bug fixed :)
Emailed support@ with the stack trace macOS provides
0 -
Thank you for letting us know, @mattbakerpdx. We'll follow up with you by email since you've contacted us over there. FWIW, my understanding is that this fix may only be part of the
Nightly
release currently, so that could explain why you're still seeing the issue.0 -
@PeterG_1P Any idea of when the next stable will release?
0