So I've been building my Mac app on our CI and sud...

# compose-desktop

[Franklin]

So I've been building my Mac app on our CI and suddenly my new Mac builds aren't launching and I see

$ /Applications/MyApp.app/Contents/MacOS/MyApp
Error occurred during initialization of VM
Could not reserve enough space for code cache (245760K)

Locally, my app builds and runs just fine. However, I don't have the certs too sign it locally. Would anyone know what's up?

I tried running a CI build using a commit from weeks ago that I know in the past has generated a perfectly normal executable/binary, and that still failed with the same error. So it's almost certainly due to some change on the CI machines, I'm just trying to narrow down what?

[Oleksandr Karpovich [JB]]

You may configure it. More info here
https://github.com/JetBrains/compose-multiplatform/tree/master/tutorials/Native_distributions_and_local_execution#customizing-launcher

[Franklin]

Ah right, I actually just tried that

jvmArgs("-XX:InitialCodeCacheSize=160K", "-XX:ReservedCodeCacheSize=32M")

Built it locally, still runs fine. Built it on CI machines and I still get

Error occurred during initialization of VM
Could not reserve enough space for code cache (32768K)

Hmm

[Franklin]

It's both built using Temurin 17.0.6

[Oleksandr Karpovich [JB]]

@alexey.tsvetkov Alexey, perhaps you may suggest some steps/ideas to investigate the issue?

Does

compose.desktop {
    application {
        jvmArgs += listOf("-Xmx2G")  // <- this
    }
}

affect the packaged (+signed) distribution? Is it applied to the packaged distribution?

[Franklin]

For what it's worth, I was poking through the code and noticed there's a log file in build/compose/tmp/createDistributable.args.txt that has

--java-options
"'-XX:InitialCodeCacheSize=160K'"
--java-options
"'-XX:ReservedCodeCacheSize=32M'"

i.e. the settings I configured. That's for running jpackage (I think).

[Franklin]

Also these are my Compose settings in build.gradle.kts

compose.desktop {
    application {
        mainClass = ""
        jvmArgs("-XX:InitialCodeCacheSize=160K", "-XX:ReservedCodeCacheSize=32M")

        nativeDistributions {
            targetFormats(TargetFormat.Dmg, TargetFormat.Msi, TargetFormat.Deb)
            packageName = ""
            packageVersion = version as String
            modules("java.sql")

            macOS {
                bundleID = ""
                iconFile.set(project.file("image/.icns"))
            }
        }
    }
}

(with some strings redacted).

[jim]

Just to clarify, you are building the app on the CI server and then running the app locally (not running the app on the CI server), right?

Shot in the dark, but is it possible this is related to entitlements? Specifically, you mention that you don't have a signing key locally, are entitlements only enforced if the app is signed? https://github.com/iterate-ch/cyberduck/issues/13347

I have no reason to believe that's the issue, other than it coming up in my search results when I did a google search, so I thought I'd mention it.

[Franklin]

Yeah I'm trying to run the app locally. That's interesting, let me try the entitlements file.

[jim]

Specifically I'm wondering if the issue is not related to the CI server, but if your local machine got an update from Apple that started being more strict about the enforcement of entitlements for signed apps. That's exactly the type of thing Apple would randomly start enforcing in an update 😛

[Franklin]

Wow yeah that did it. Thanks so much @jim

Embarrassed to say I did not check the Google results that far down lol.

[jim]

👍 Glad it's working for you! Happy composing!

[spierce7]

@Franklin I'm encountering the same issue. How did you solve this?

[Franklin]

Create a file default.entitlements or whatever you want to name it

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "<http://www.apple.com/DTDs/PropertyList-1.0.dtd>">
<plist version="1.0">
<dict>
    <key>com.apple.security.cs.allow-jit</key>
    <true/>
    <key>com.apple.security.cs.allow-unsigned-executable-memory</key>
    <true/>
    <key>com.apple.security.cs.disable-library-validation</key>
    <true/>
</dict>
</plist>

In your build.gradle.kts file add

compose.desktop {
    application {
        mainClass = ""

        nativeDistributions {
            targetFormats(TargetFormat.Dmg, TargetFormat.Msi, TargetFormat.Deb)
            packageName = ""
            packageVersion = version as String

            macOS {
                bundleID = ""
                iconFile.set(project.file(""))
                entitlementsFile.set(project.file("default.entitlements")) // <----------- this line
            }
        }
    }
}

[spierce7]

All of these entitlements are required for compose desktop?

[jim]

Those look like they are entitlements required to run a JVM. None of those look compose-specific. Compose for desktop just happens to use a JVM.

[spierce7]

I've never even heard of entitlements. This is new to me. Thanks for the easy instructions. Giving it a shot now.

[spierce7]

LOL you have to explicitly allow a JIT