New assembler crashes on M1 in x64

[haraldsteinlechner]

Seems new after updates, in PRo3D on Mac M1 running in rosetta we get:

@krauthaufen this is a new assembler which got active, right? could one switch to real ARM64 yet? pro3d-space/PRo3D#197

[krauthaufen]

So far everything worked on ARM64, so I think we could give it a try

[haraldsteinlechner]

it is a lot of work to get native arm64 though (pro3d side, other libs etc). could be step 2. ideas why x64 is broken? it might also be broken on native x64 Macs?

[haraldsteinlechner]

seems like eiswriteable is not available in jitmem. is this just a wrong version being used or something?

[krauthaufen]

Looks like it, i added the entrypoint in one of the last versions

[krauthaufen]

Maybe there was a broken version which got resolved at your end? Is there a newer one?

[haraldsteinlechner]

i is 5.2.12 rendering. if there is a newer one maybe @laurafritz or @hyazinthh could upgrade. i need to hand this one over... thanks you all

[haraldsteinlechner]

https://github.com/pro3d-space/PRo3D/blob/develop/paket.lock assembler is 0.0.7 btw

[haraldsteinlechner]

ah and another info. on win this exact build works...

[krauthaufen]

Maybe related: aardvark-platform/aardvark.docs#34

[haraldsteinlechner]

fix for amd64 Mac is in the assembler package, not sure about deployment though

[haraldsteinlechner]

status:

• aardvark.assembler 0.0.7, the embedded version has eiswriteable
• pro3d is using 0.0.7
• yet is seems to load a native lib which is packaged in aardvark.rendering according to this output

 6: [Introspection] loaded native library jitmem.dylib from /var/folders/ls/fc80rh9d40vbtn23g92pvcjh0000gn/T/aardvark-native/Aardvark.Rendering.GL-04c7c946-bb69-d9ba-c36b-1d07d22d1550-64/libjitmem.dylib
 6: [Introspection] loaded native library jitmem from jitmem.dylib
 6: ERROR
 6:   [Client] 2: rendering faulted with System.TypeInitializationException: The type initializer for 'Aardvark.Assembler.JitMem' threw an exception.
 6:    ---> System.TypeInitializationException: The type initializer for '<StartupCode$Aardvark-Assembler>.$JitMem' threw an exception.
 6:    ---> System.EntryPointNotFoundException: Unable to find an entry point named 'eiswritable' in shared library 'jitmem'.
 6:      at Aardvark.Assembler.JitMem.eiswritable()
 6:      at <StartupCode$Aardvark-Assembler>.$JitMem..cctor()
 6:      --- End of inner exception stack trace ---
 6:      at Aardvark.Assembler.JitMem..cctor()
 6:      --- End of inner exception stack trace ---

shouldn't this one be unpacked from aardvark.assembler?� it seems to be using rendering 5.2.12. could rendering upgrade just fix this one? pro3d-space/PRo3D#227

[haraldsteinlechner]

it seems like this aardvark.rendering version is taking jitmem.dylib from aardvark.rendering instead of aardvark.assembler - 5.3 prerelease track could fix this issue, unfortunately pro3d is blocked. what is the last eiswritable free version to downforce rendering? other option would be to backport the new assembler to non 5.3 or upgrade pro3d to 5.3

[krauthaufen]

The rendering dylib shouldn't exist anymore, so we can just remove it and publish a new minor rendering version?

[haraldsteinlechner]

yes, was already done, created a new package. works