Fata IDE crash on build

Hi all,

I must have made some change to a web app that was working fine, but for the life of me can’t understand what is crashing the IDE.

When I build/run the project, the IDE crashes fatally with the error message:

The crashed thread data

OS Version: macOS 15.5 (24F74)
Report Version: 12
Anonymous UUID: 1199C12C-4C35-8035-05F2-64FA4943A752

Sleep/Wake UUID: AC48E5D1-7AB7-4177-B571-1AD8DDAD581D

Time Awake Since Boot: 680000 seconds
Time Since Wake: 4719 seconds

System Integrity Protection: enabled

Crashed Thread: 0

Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000

Thread 0 Crashed:
0 libsystem_kernel.dylib 0x18eba5388 0x18eb9c000 + 37768
1 libsystem_c.dylib 0x18eae7c60 0x18ea6f000 + 494688
2 libsystem_c.dylib 0x18eae6eec 0x18ea6f000 + 491244
3 XojoFramework 0x113c94d7c CocoaAssertionDialog::AssertFired(char const*, char const*, int, char const*, char const*) + 448
4 SpawnCompiler.dylib 0x12ca13988 0x12b900000 + 17906056
5 SpawnCompiler.dylib 0x12c9d2c74 0x12b900000 + 17640564
6 Xojo 0x1052c8b44 0x104db0000 + 5344068
7 Xojo 0x108afffc0 0x104db0000 + 64290752
8 Xojo 0x1109c7d30 0x104db0000 + 197229872
9 Xojo 0x1109b95c0 0x104db0000 + 197170624
10 Xojo 0x11099d488 0x104db0000 + 197055624
11 Xojo 0x110868320 0x104db0000 + 195789600
12 Xojo 0x11084eb64 0x104db0000 + 195685220
13 Xojo 0x10561aa98 0x104db0000 + 8825496
14 Xojo 0x1108418a4 0x104db0000 + 195631268
15 Xojo 0x10896c434 0x104db0000 + 62637108
16 Xojo 0x10899b570 0x104db0000 + 62829936
17 Xojo 0x1089a5b60 0x104db0000 + 62872416
18 Xojo 0x1089a017c 0x104db0000 + 62849404
19 Xojo 0x1096ee964 0x104db0000 + 76802404
20 Xojo 0x106477680 0x104db0000 + 23885440
21 Xojo 0x1064781e4 0x104db0000 + 23888356
22 Xojo 0x1096afc7c 0x104db0000 + 76545148
23 XojoFramework 0x113dbffc0 InvokeMenuHandler(RunMenuItem*, unsigned char, Window*, unsigned char&) + 1008
24 XojoFramework 0x113dc0288 RuntimeMenuItemClick(RunMenuItem*, unsigned char, Window*, unsigned char*) + 128
25 XojoFramework 0x113cb781c CocoaMenu::_MenuItemAction(NSMenuItem*) + 76
26 XojoFramework 0x113cb7e84 0x113bf0000 + 818820
27 AppKit 0x192d8f020 0x192bb5000 + 1941536
28 AppKit 0x192e572d8 0x192bb5000 + 2761432
29 AppKit 0x1935ba510 0x192bb5000 + 10507536
30 AppKit 0x19340e7f0 0x192bb5000 + 8755184
31 AppKit 0x192e5632c 0x192bb5000 + 2757420
32 AppKit 0x19358f108 0x192bb5000 + 10330376
33 AppKit 0x19358cfdc 0x192bb5000 + 10321884
34 XojoFramework 0x113cd69ac 0x113bf0000 + 944556
35 Xojo 0x105031de8 0x104db0000 + 2629096
36 XojoFramework 0x113e61d24 CallFunctionWithExceptionHandling(void (*)()) + 180
37 XojoFramework 0x113cd695c 0x113bf0000 + 944476
38 AppKit 0x19318c42c 0x192bb5000 + 6124588
39 AppKit 0x192be2c8c 0x192bb5000 + 187532
40 XojoFramework 0x113e60414 RuntimeRun + 60
41 Xojo 0x1051faf30 0x104db0000 + 4501296
42 Xojo 0x111c18ca4 0x104db0000 + 216435876
43 Xojo 0x111bf3034 0x104db0000 + 216281140
44 dyld 0x18e83eb98 0x18e838000 + 27544

I can’t see what I would have changed to cause this… any pointers? (no pun intended!)

Many thanks,
Stam

What version of Xojo?

2025 Release 1.1

Don’t know how much help you’ll get with this here. I can’t think of anything that would cause the compiler to behave this way from a project source perspective. Best bet would be to open an Issues case and submit a project that reproduces the error. If you can’t reproduce the issue in a minimal project, you can make the case private.

I’m wondering if you’re using any structures. I’ve seen those render weird in the past.

Thanks @Anthony_G_Cyphers
No, not using structures.

I can open and run a previous version of the project which is not much different without a crash but not sure what the actual differences in code are. Also not sure how best to check given the very large number of locations containing code, is there an easy way to do a project-wide diff in Xojo?

If you use source control, IE: git, (which you should be), you should be able to view a diff of the project, assuming you’re not using the binary project format (which you shouldn’t). Could more easily pinpoint the change that way.

yeah… I had been using an xml version but sometime previously I unconsciously saved as binary (must have been a default choice or something).
Guess I’m out of luck and will have to manually check…

Yeah, that’s not fun. Please be sure to post the Issues case link here once you create one. I’m interested in what’s causing the renderer to freak out.

If possible, open a private case. You found something that Xojo wasn’t expecting to see, but had a guard just in case.

Save default choice ?
As far as I remember, the default is the last you save.

Working with XML version is not a good idea… use binary of Xojo (text).

Do you reboot your computer and try to compile again ?

So the IDE feeds the project to the compiler.
It feeds multi line text where that is not expected.

Probably you have. field in the IDE, where you have a return character where you should not have one.

e.g. You copy & pasted some text into a field for a property and that includes the return.

1 Like

It was a restore from a crash - I did a ‘save as’ and must have unthinkingly just gone with whatever it served up.

Since I didn’t have this on my GitHub I just ignored that but now I obviously regret this and will export the immediately previous working version to my GitHub.

I really should have known better I suppose…

I reproduced it and reported the issue:

#79389 Xojo crashes with a two line text as application identifier in web project

2 Likes

@Stam_Kapetanakis

Launch the IDE from a terminal window and then open and build your project. You may get more information in there. Just type the word “open” followed by a space and then drag and drop the Xojo.app bundle onto the terminal window.

You somehow beat me to it!
I had submitted the issue here: xojoinc/xojo#79390

@Christian_Schmitz - how did you create this error?

I copied a return character (Char 13) and pasted it into the application identifier field and hit build.

And I may suggest you start using version control with e.g. GIT, so while you work on a webpage and then save it, you may see that you accidentally broke something in a different module. This way you could easily prevent or reverse.

2 Likes