2026 R2 New Bugs?

[Marius_Dieter_Noetzel]

Since 2026R2 one of my macos Apps produce this error without any information in the Debugger-window. Is this something new, or just something I#ve newer seen before?

[kevin_g]

Seems similar to the issue discussed here.

How to close a window in 2026r2 without crashing

I’m still working on the crashes in 2026r2. One remaining crash happens when closing windows. I had some rather old window menu which I took out. The new code for closing is much more simple: Function WindowCloseWindow() As Boolean // Closes the frontmost document window from the Window menu. Dim FrontWindow As Window = App.FirstDocumentWindow If FrontWindow <> Nil Then FrontWindow.Close Return True exception exc theException = new ErrorException(exc, currentMethodName) End Fun…

[Thomas_Kaltschmidt]

Is this inside an event? May this way should be more safe:

Timer.CallLater(0, AddressOf DoClose)

Sub DoClose()
  Self.Close
End Sub

[Beatrix_Willius]

Closing windows is extremely iffy in 2026r2. I made one ticket earlier today but this applies only to a very complicated window. I fixed other crashes like quitting with 2 windows open. Or closing a window inside the close event.

Please post your crash log. To get the crash log uncheck “Break on fatal error” in the menu (learned that today).

[Henry_F_Gibson]

Happens to me using a modal window with code I’ve been using since 2011. Instead of self.close I’m using self.hide and that seems to “work”.

I’m going back to 2025 until it’s fixed.

[Julia_Truchsess]

I get these access violations occasionally with 2026 r1.2. It feels like they’re often related to CURLSMBS, e.g. I was getting them frequently when using Curl.PerformMT (I think the “bomb” icon appeared on that line) and when I changed it to Perform, they stopped. Possibly related to mixing usage of CURLSMultiMBS.SharedInstance with other means of dispatching curls, but I admit I’m grasping at straws.

[Stephen_Dodd]

For what it’s worth, I had a hard crash when closing a window on a SMTPSecureSocket event. If I closed the socket before closing the window, it fixed it.