https://bz.apache.org/ooo/show_bug.cgi?id=128617
--- Comment #19 from Alexbaron309 <[email protected]> --- (In reply to Arrigo Marchiori from comment #17) I will try and will update this bug report aswell. > I tried to run a build of AOO41X on an Intel Mac and I got the following on > stderr, when I clicked Help -> Check for Updates: > > 2025-09-18 16:26:49.187 soffice[24054:18464210] WARNING: NSWindow drag > regions should only be invalidated on the Main Thread! This will throw an > exception in the future. Called from ( 0 AppKit > 0x00007fff329039a9 -[NSWindow(NSWindow_Theme) > _postWindowNeedsToResetDragMarginsUnlessPostingDisabled] + 371 > 1 AppKit 0x00007fff328eb3d2 > -[NSWindow _initContent:styleMask:backing:defer:contentView:] + 1416 > 2 AppKit 0x00007fff328eae43 > -[NSWindow initWithContentRect:styleMask:backing:defer:] + 42 > 3 libvcl.dylib 0x0000000110112d25 > -[SalFrameWindow initWithSalFrame:] + 213 > 4 libvcl.dylib 0x000000010fe56c38 > _ZN12AquaSalFrame17initWindowAndViewEv + 568 > 5 libvcl.dylib 0x000000010fe566d1 > _ZN12AquaSalFrameC2EP8SalFramem + 513 > 6 libvcl.dylib 0x000000010fe32060 > _ZN15AquaSalInstance11CreateFrameEP8SalFramem + 48 > 7 libvcl.dylib 0x00000001100decf3 > _ZN6Window8ImplInitEPS_lP16SystemParentData + 1043 > 8 libvcl.dylib 0x000000011006b715 > _ZN6Dialog8ImplInitEP6Windowl + 453 > 9 libvcl.dylib 0x000000011006bc1b > _ZN6DialogC1EP6Windowl + 155 > 10 libootk.dylib 0x000000010f57e95f > _ZN11VCLXToolkit16ImplCreateWindowEPP10VCLXWindowRKN3com3sun4star3awt16Window > DescriptorEP6Windowl + 255 > 11 libootk.dylib 0x000000010f57e206 > _ZN11VCLXToolkit16ImplCreateWindowERKN3com3sun4star3awt16WindowDescriptorEl > + 246 > 12 libootk.dylib 0x000000010f57e5c4 > _ZThn80_N11VCLXToolkit12createWindowERKN3com3sun4star3awt16WindowDescriptorE > + 20 > 13 libootk.dylib 0x000000010f640b13 > _ZN10UnoControl10createPeerERKN3com3sun4star3uno9ReferenceINS2_3awt8XToolkitE > EERKNS4_INS5_11XWindowPeerEEE + 2579 > 14 libootk.dylib 0x000000010f64934f > _ZN19UnoControlContainer10createPeerERKN3com3sun4star3uno9ReferenceINS2_3awt8 > XToolkitEEERKNS4_INS5_11XWindowPeerEEE > + 143 > 15 libootk.dylib 0x000000010f5e9416 > _ZN16UnoDialogControl10createPeerERKN3com3sun4star3uno9ReferenceINS2_3awt8XTo > olkitEEERKNS4_INS5_11XWindowPeerEEE + 5 > 4 > 16 updchk.uno.dylib 0x00000001176ce063 > _ZN13UpdateHandler12createDialogEv + 16659 > 17 updchk.uno.dylib 0x00000001176c9c8f > _ZN13UpdateHandler10setVisibleEb + 63 > 18 updchk.uno.dylib 0x00000001176b8935 > _ZN11UpdateCheck10showDialogEb + 245 > 19 updchk.uno.dylib 0x00000001176be77c > _ZN12_GLOBAL__N_124InitUpdateCheckJobThread3runEv + 76 > 20 libsofficeapp.dylib 0x000000010e4119af > threadFunc + 15 > 21 libuno_sal.dylib.3 0x000000010e190b69 > osl_thread_start_Impl + 233 > 22 libsystem_pthread.dylib 0x00007fff6f5df109 > _pthread_start + 148 > 23 libsystem_pthread.dylib 0x00007fff6f5dab8b > thread_start + 15 > ) > > The same binary on a M1 Mac hangs (just?) before emitting such a warning. I > could find the invocation of "showDialog" also in the stack trace at comment > #16. > > To me, it looks like a window created on a thread. Can we call GUI functions > in MacOS from non-main threads at all? > > In order to reproduce the above, I had to wait for some time until the > automatic updates were executed. Then, click Help -> Check for updates. > > I hope this helps. -- You are receiving this mail because: You are the assignee for the issue.
