I have a user reporting a problem my software freezes while generating text file in user selected path (spinning ball of death)
On my own Intel 64bit Big Sur it works
- signed one year old release executable
- freshly compiled debug build on Trunk FPCUPdeluxe 2.4.0g x86_64 darwin-cocoa
However, my Lazarus states in about
2025-11-12
Lazarus_3_2
FPC 3.2.2
So apparently newest trunk version?
From user description: I would guestimate it could some string handling code getting lost looping in a huge amount of memory.
Are there any known issues regarding
1) Intel code generated and the ARM rosetta2 intel emulator/virtual?
2) Some API in Sequoia with stricter file access? (Chatgpt seems to thing file security been beefed up and there are certain flags with dialogs for selecting directory that has changed)
3) Maybe something with Sequoia and UTF8 and string libraries?
Any ideas from where to start to look?