You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have Azure DevOps pipelines compiling a .NET 8 application for iOS and Android. Since the last macOS update (15.3), our pipelines are failing inconsistently—sometimes during the restore step and sometimes during the build step. Azure agents are on version 3.238.0
Here’s an example of the error we get when installing the iOS workload:
/xxxx/sds-azure-agent/agent/_work/_tool/dotnet/dotnet workload install ios
dotnet(55273,0x1edec4840) malloc: Unrecognized value for MallocDebugReport (1) - using 'stderr'
dotnet(55273) MallocStackLogging: could not tag MSL-related memory as no_footprint, so those pages will be included in process footprint - (null)
dotnet(55273) MallocStackLogging: stack logs being written to /private/tmp/stack-logs.55273.105074000.dotnet.8X77wI.index
dotnet(55273) MallocStackLogging: recording malloc and VM allocation stacks to disk using standard recorder
dotnet(55273,0x16b4db000) malloc: *** error for object 0x600003c0a0e0: pointer being freed was not allocated
dotnet(55273,0x16b4db000) malloc: *** set a breakpoint in malloc_error_break to debug
[1] 55273 abort /xxx/sds-azure-agent/agent/_work/_tool/dotnet/dotnet
We have Azure DevOps pipelines compiling a .NET 8 application for iOS and Android. Since the last macOS update (15.3), our pipelines are failing inconsistently—sometimes during the restore step and sometimes during the build step. Azure agents are on version 3.238.0
Here’s an example of the error we get when installing the iOS workload:
We use the following task to install dotnet-sdk:
This task works on both macOS versions, but we noticed that the workload version differs, which might be causing the issue.
On Macos 15.2 we have:
On Macos 15.3 we have:
An this is what we do during restore task for iOS apps:
For Android apps:
And our workload-manifest:
Does anyone have an idea what might be causing this issue? Could it be related to the workload version differences or a change in macOS 15.3?
Thank you! 🙏
The text was updated successfully, but these errors were encountered: