So far consistently on macOS 11.1 (20C69) and across both X86-64 (Native) / ARM-64 on the main thread 0 with nothing in the traces from the extension itself.
Several nearly identical stack traces on the developer forms for safari extensions seem to indicate this may be a known issue upstream from the extension?
So far consistently on macOS 11.1 (20C69) and across both X86-64 (Native) / ARM-64 on the main thread 0 with nothing in the traces from the extension itself.
Several nearly identical stack traces on the developer forms for safari extensions seem to indicate this may be a known issue upstream from the extension?