Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Worklets installation not working. Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 17909 (mqt_js)

Abierto
#111 4 comentarios 2 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
35/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
android, javascript, react-native
Área
mobile

Línea de trabajo

Start with the JavaScript reproduction using Worklets.createRunInContextFn and the manual MainApplication.java setup, then inspect the Android logcat output around the SIGABRT on the mqt_js thread. Done means the Fibonacci example executes successfully without the fatal signal in a project that is not using React Native's new architecture.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Hello Team

Thanks for bringing this package. I've been trying to install it in my JavaScript project (no typescript) and I've been having issues not being able to execute the example.
I've installed it, manually linking it (my project has problems with auto-linking, so I manually added it to the MainApplication.java file). It seems to be capturing the function correctly, but it fails with an error Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 17909 (mqt_js) when executing the code.

I'm trying the example as follows:

import { Worklets } from 'react-native-worklets-core'

const fibonacci = (num) => {
        'worklet'
        if (num <= 1) return 1
        return fibonacci(num - 1) + fibonacci(num - 2)
}
              
const worklet = Worklets.createRunInContextFn(fibonacci)
            
worklet(50).then((result) => {
       console.log(`Fibonacci of 50 is ${result}`)
})

There shouldn't be a difference compared to the example typescript one, except for removing the types.

This is the error I see in my console, before it crashes
image

And this is the logcat

09-04 12:07:20.747 17673 17909 F libc    : Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 17909 (mqt_js), pid 17673 (package.name)
09-04 12:07:20.784 18125 18125 F DEBUG   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
09-04 12:07:20.784 18125 18125 F DEBUG   : Build fingerprint: 'google/sdk_gphone_x86/generic_x86_arm:11/RSR1.201013.001/6903271:user/release-keys'
09-04 12:07:20.784 18125 18125 F DEBUG   : Revision: '0'
09-04 12:07:20.784 18125 18125 F DEBUG   : ABI: 'x86'
09-04 12:07:20.784 18125 18125 F DEBUG   : Timestamp: 2023-09-04 12:07:20-0500
09-04 12:07:20.784 18125 18125 F DEBUG   : pid: 17673, tid: 17909, name: mqt_js  >>> com.app.name <<<
09-04 12:07:20.784 18125 18125 F DEBUG   : uid: 10163
09-04 12:07:20.784 18125 18125 F DEBUG   : signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr --------
09-04 12:07:20.784 18125 18125 F DEBUG   :     eax 00000000  ebx 00004509  ecx 000045f5  edx 00000006
09-04 12:07:20.784 18125 18125 F DEBUG   :     edi f351e81e  esi be2a6130
09-04 12:07:20.784 18125 18125 F DEBUG   :     ebp f4ca6b90  esp be2a60d8  eip f4ca6b99
09-04 12:07:20.786 18125 18125 F DEBUG   : backtrace:
09-04 12:07:20.786 18125 18125 F DEBUG   :       #00 pc 00000b99  [vdso] (__kernel_vsyscall+9)
09-04 12:07:20.786 18125 18125 F DEBUG   :       #01 pc 0005ad68  /apex/com.android.runtime/lib/bionic/libc.so (syscall+40) (BuildId: 6e3a0180fa6637b68c0d181c343e6806)
09-04 12:07:20.786 18125 18125 F DEBUG   :       #02 pc 00076511  /apex/com.android.runtime/lib/bionic/libc.so (abort+209) (BuildId: 6e3a0180fa6637b68c0d181c343e6806)

Is there something I'm missing here?
Also, I'm not using React's new architecture

Thank you!

Lenguaje dominante
C++
Estrellas
791
Forks
65
Métricas de merge de PR
Sin PR fusionados en 30 d

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de margelo/react-native-worklets-core

Todos los issues de margelo/react-native-worklets-core

Issues similares

Más issues de C++

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.