Hi I just upgraded from 1.65 on Chromebook to 1.66. Now the application will not open, I get a window briefly then it closes. I’m using the google play store to install nomad as a android app on the chromebook.
I had a sculpt open when it was closed as 1.65.
I have tried uninstalling and reinstalling the app, still crashes upon open.
I’m using a Acer Chromebook Spin 713 CP713-2W-568T (10th gen I5 / 16GB of RAM / 256 SSD) and the latest version of Chromeos.
Did you delete the data when you tried to reinstall it?
Yes I just deleted all the data, including the app cache, still crashes on open
10-20 20:23:36.679 3354 3375 I nomad : GPU vendor: Mesa/X.org
10-20 20:23:36.680 3354 3375 I nomad : GPU renderer: virgl (Mesa DRI Intel(R) UHD Graphics (CML GT2))
10-20 20:23:36.680 3354 3375 I nomad : GL version: OpenGL ES 3.1 Mesa 22.0.0-rc2 (git-b39d467a8b)
10-20 20:23:36.680 3354 3375 I nomad : GLAD version: 3.1
10-20 20:23:36.680 3354 3375 I nomad :
10-20 20:23:36.680 3354 3375 I nomad : hasMapBufferRange Yes
10-20 20:23:36.680 3354 3375 I nomad : hasDepthClamp Yes
10-20 20:23:36.681 3354 3375 I nomad : hasConservativeDepth No
10-20 20:23:36.681 3354 3375 I nomad : hasDisjointQuery Yes
10-20 20:23:36.681 3354 3375 I nomad : hasBufferStorage No
10-20 20:23:36.681 3354 3375 I nomad : hasDebug No
10-20 20:23:36.681 3354 3375 I nomad : hasComputeShader Yes
10-20 20:23:36.681 3354 3375 I nomad : hasRenderNorm16 Yes
10-20 20:23:36.681 3354 3375 I nomad :
10-20 20:23:36.687 3354 3375 F libc : Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 3375 (GLThread 41), pid 3354 (aneginier.nomad)
10-20 20:23:36.703 3383 3383 I crash_dump64: obtaining output fd from tombstoned, type: kDebuggerdTombstone
10-20 20:23:36.703 202 202 I tombstoned: received crash request for pid 3375
10-20 20:23:36.703 3383 3383 I crash_dump64: performing dump of process 3354 (target tid = 3375)
10-20 20:23:36.707 3383 3383 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
10-20 20:23:36.707 3383 3383 F DEBUG : Build fingerprint: ‘google/hatch/hatch_cheets:11/R106-15054.114.0/9138518:user/release-keys’
10-20 20:23:36.707 3383 3383 F DEBUG : Revision: ‘0’
10-20 20:23:36.707 3383 3383 F DEBUG : ABI: ‘x86_64’
10-20 20:23:36.707 3383 3383 F DEBUG : Timestamp: 2022-10-20 20:23:36-0600
10-20 20:23:36.707 3383 3383 F DEBUG : pid: 3354, tid: 3375, name: GLThread 41 >>> com.stephaneginier.nomad <<<
10-20 20:23:36.707 3383 3383 F DEBUG : uid: 10109
10-20 20:23:36.707 3383 3383 F DEBUG : signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr --------
10-20 20:23:36.707 3383 3383 F DEBUG : rax 0000000000000000 rbx 0000000000000d1a rcx 00007bb48fba33d8 rdx 0000000000000006
10-20 20:23:36.707 3383 3383 F DEBUG : r8 0000000000000000 r9 0000000000000000 r10 00007bb3fcdf4f80 r11 0000000000000246
10-20 20:23:36.707 3383 3383 F DEBUG : r12 00007bb3fcdfb760 r13 0000000000000056 r14 00007bb3fcdf4f78 r15 0000000000000d2f
10-20 20:23:36.707 3383 3383 F DEBUG : rdi 0000000000000d1a rsi 0000000000000d2f
10-20 20:23:36.707 3383 3383 F DEBUG : rbp 00007bb404210640 rsp 00007bb3fcdf4f68 rip 00007bb48fba33d8
10-20 20:23:36.740 3383 3383 F DEBUG : backtrace:
10-20 20:23:36.740 3383 3383 F DEBUG : #00 pc 000000000009c3d8 /apex/com.android.runtime/lib64/bionic/libc.so (syscall+24) (BuildId: f5a3211312b9b08fe4406798662fbabb)
10-20 20:23:36.740 3383 3383 F DEBUG : #01 pc 000000000009f282 /apex/com.android.runtime/lib64/bionic/libc.so (abort+194) (BuildId: f5a3211312b9b08fe4406798662fbabb)
10-20 20:23:36.740 3383 3383 F DEBUG : #02 pc 00000000003539bf /vendor/lib64/libhoudini.so (BuildId: a15904553aadfaa2f7d687f3509c4c1ae1be5bfb)
10-20 20:23:36.740 3383 3383 F DEBUG : #03 pc 00000000003040e5 /vendor/lib64/libhoudini.so (BuildId: a15904553aadfaa2f7d687f3509c4c1ae1be5bfb)
10-20 20:23:36.740 3383 3383 F DEBUG : #04 pc 000000000038a4d8 /vendor/lib64/libhoudini.so (BuildId: a15904553aadfaa2f7d687f3509c4c1ae1be5bfb)
10-20 20:23:36.740 3383 3383 F DEBUG : #05 pc 000000000038a219 /vendor/lib64/libhoudini.so (BuildId: a15904553aadfaa2f7d687f3509c4c1ae1be5bfb)
10-20 20:23:36.741 3383 3383 F DEBUG : #06 pc 000000000038df4d /vendor/lib64/libhoudini.so (BuildId: a15904553aadfaa2f7d687f3509c4c1ae1be5bfb)
10-20 20:23:36.919 202 202 E tombstoned: Tombstone written to: /data/tombstones/tombstone_12
Thanks but it’s looking bad.
I couldn’t replicate the crash on any of my Android devices.
And the issue doesn’t seem widespread, probably a chromebook thing only.
Any other debugging I can do on my end to help resolve it?
For now I don’t think so.
I’m waiting to see if the crash reports appear in my Google Play developer console thing.
For now the stack trace is not helpful 
It’s crashing in libhoudini, which is basically the thing that translates ARM binaries into x86_64.
Is the web version working? nomad - WebAssembly
Ok, yeah I stupidly dismissed the dialog to report the crash to the developer, and have no idea how to trigger it again.
The web assembly version works.
I have an old arm chromebook I’ll try it on, if it works there then I’ll report it as an issue against libhoudini
Yep, it works on the old arm chromebook, the only immediate fix I could see on your end is to cross compile an intel library for what ever your using that is native arm code.
This is furstrationing, Nomad sculpt 1.65 worked really well on my newer intel chromebook, it’s a good platform for 3D stuff since you can natively run linux along android apps. My work flow invovles bouncing between different 3D apps on the chromebook, i.e. nomad, openscad, blender, 3dcoat, f3d, cura, etc, and it’s stylus support is pretty good.
I’m gonna see if I can sideload the nomad 1.65 from my arm chromebook …
Well everything is native, but I only provide arm8 and arm7 binaries for Android.
I’m going to include x86_64 but there’s no guarantee it’s going to work if it crashes on the graphical side of thing.
Thank you!
One other question I assume this will be part of the 1.67 release? I’m wondering when or how I can help test it.
1.67 is under review on Google Play.
Hopefully your intel chrome should select the x86_64 abi.
If it still doesn’t work, you can check if the call stack is different.
That fixed it! Thank you!
Oh great.
In theory it should also be faster as well, but I don’t know how robust libhoudini is.
Yeah I wasn’t certain if you’re still doing all your development in javascript. I actually spent lots of time trying to understand your sculptgl code. I really wanted something like nomad sculpt, and you built it!
A while ago when I was inbetween jobs, I built a vulkan based tool in go, I wanted to make a tool to make patterns for sewing from 3d objects, but my background isn’t in 3D so it’s a steep hill to climb development wise.
Uptil this release I hadn’t had any problems using the intel based chromebook, like I said it’s been a pretty good mobile 3D hardware platform.