TheTomas here (GNU/LInux Debian stable) it doesn't crash but I get the message: [Error] App exited with code 1 before connecting to the profiler. Fatal: failed to start profiler: The Objo profiler assembly could not be found. even for Objo examples.
Richard_And_Trisha TheTomas I got the same error on my macOS Tahoe 26.5.2 with 48GB RAM Mac mini Apple M4 Pro chip I got the error the minute I click on profile button.
Garry Yeah. I tweaked my automation for packaging and didn't include the profiler assembly so it's non-functional on every platform. I'm currently rebuilding all the artefacts and hardening the automation. 26.7.4 will be out later today with the fix. It takes a few hours to build though.
bgrommes Garry I've been using the profiler without incident on Windows, but with a pre-existing project. Maybe it works because I'm installing from the special portable zip install??
Garry Thanks for the info. This is proving to be an extremely difficult issue to pin down. Everything works great on my dev machine but the issue has been that the profiler is dynamically loaded into a trimmed bundled host. It's requiring many incantations to get it working in a signed app. I'm almost there and hopeful to have the fix out today. The trouble is I can only 100% verify the fix when all artefacts are built and trimmed and that takes a few hours for each run.
bgrommes Garry Loving craftsmanship and attention to detail. This is The Way. Even when it's hard. I (and I'm sure, we) so appreciate what you're doing :-)
Garry I think I've cracked it! Just uploading the artefacts now and adjusting the release manifest. Should be live within the hour
Garry I’ve certainly had quieter Sundays! I’ve made some robust changes to my deployment policies to prevent a goof like this in the future.
