omp_pause_resource() warning on every SparseArray.Call() with the clang/libomp toolchain (Windows arm64)
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 35/100
Línea de trabajo
Start with .pause_resource() in R/thread-control.R, which warns on a non-zero return, and its C counterpart in src/thread_control.c, which calls omp_pause_resource(). Check where SparseArray.Call() invokes it in its on.exit(). Reproduce by running the NaArray-Arith-methods example, which should warn on a clang/libomp build. Done means the example and the test suite run without the warning, and the choice between the four proposed fixes is agreed on in the thread.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
On the Windows arm64 builder at R-Universe, SparseArray 1.13.4 emits the following warning on almost every call into its C code (see log here):
Warning in .pause_resource() :
omp_pause_resource() failed to relinquish resources on device 0
The x86_64 Windows build of the same version is silent. The results themselves are correct and only the warnings differ. However, the warnings reach downstream packages. For example, GSVA's unit tests for version 2.7.23 failed on Windows arm64 because one test was turning such a warning into an error. I have tweaked the test in GSVA to make it pass, but other packages may run into it too.
Minimal reproducible example
I don't have a Windows machine, so this is more of a guess based on the outputs of the logs from R-Universe and suggestions by Claude Code, taking SparseArray's own NaArray-Arith-methods example, which warns in the arm64 example log:
library(SparseArray)
nam1 <- NaArray(dim=c(15, 6), type="integer")
nam1[cbind(1:15, 2)] <- 100:114
## Warning in .pause_resource() :
## omp_pause_resource() failed to relinquish resources on device 0
nam1[cbind(1:15, 5)] <- -(114:100)
## Warning in .pause_resource() : ...
nam1
## Warning in .pause_resource() : ...
Calling the internal wrapper directly should isolate the cause:
SparseArray:::.pause_resource() # expected to return 0
SparseArray:::.pause_resource() # expected to warn: runtime already paused
Possible cause
SparseArray.Call() always runs .pause_resource() in its on.exit(). That calls omp_pause_resource(omp_pause_soft, omp_get_initial_device()) (src/thread_control.c) and warns whenever the return value is non-zero (R/thread-control.R).
The return value depends on the OpenMP runtime:
- libgomp (GCC): pausing the host always succeeds and returns 0, unless it's called inside a parallel region. That's why Linux and Windows x86_64 builds are silent. macOS builds without OpenMP are unaffected.
- LLVM libomp (clang): as far as Claude can tell from the libomp sources (
__kmp_pause_resource()inkmp_runtime.cpp), a pause request returns non-zero if the runtime is already paused. A soft pause is only lifted when the next parallel region starts (__kmp_resume_if_soft_paused()).
Only a few C files contain #pragma omp parallel regions (SparseMatrix_mult.c, SparseArray_subassignment.c, SparseArray_matrixStats.c, SparseArray_subsetting.c). Most SparseArray.Call()s never open one, so after the first soft pause the runtime stays paused. Every later omp_pause_resource() call then fails as "already paused" and triggers the warning. This should affect any clang + libomp build, such as Linux with clang or macOS with OpenMP enabled, not only Windows arm64.
Possible fixes
- Treat the pause as best-effort: ignore the return value of
omp_pause_resource(), or report it only once or when a verbose/debug option is set. - Only call
.pause_resource()after C routines that actually ran a parallel region, or keep a flag in C that is set when a parallel region is entered. - Skip the pause when
nthread <= 1, since no worker threads were created. - Check the pause state before pausing again, so an already-paused runtime isn't treated as an error.
Unrelated, minor
Both Windows builders also report an install WARNING for -Wformat at OPBufTree.c:320 (%lu) and SVT_SparseArray_class.c:677-679 (%ld). Both print an R_xlen_t (long long), but long is 32-bit on Windows, so large values could be printed wrong. Casting to (long long) with %lld, or to (double) with %.0f, would fix it.
This issue has been written with the assistance of Claude Code (Anthropic).
- Lenguaje dominante
- C
- Estrellas
- 13
- Forks
- 3
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Preparar el entorno
Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de Bioconductor/SparseArray
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 35/100
Bioconductor/SparseArray#20 · 3 comentarios ·
-
enhancement
Dificultad 5/5 Más de una semana Aptitud para principiantes 25/100
Bioconductor/SparseArray#5 · 7 comentarios · 1 reacción ·
Todos los issues de Bioconductor/SparseArray
Issues similares
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
Los mantenedores suelen responder en 1 día
-
enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
ChupathingyCE/chupathingyce#1550 ·
Los mantenedores suelen responder en 1 día
-
[BUG] SWAPDB sends no invalidation to CLIENT TRACKING clientsPosiblemente ocupada Un pull request vinculado a esta issue está abierto o ya se fusionó. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 83/100
redis/redis#16302 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
slice
Dificultad 2/5 1-3 horas Aptitud para principiantes 73/100
Life-Framework/Life-Framework#3878 ·
Los mantenedores suelen responder en 1 día
-
`sha256()` returns a wrong hash when libsql-ffi is built with gcc 11 or laterPosiblemente ocupada @colinhacks la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
tursodatabase/libsql#2333 ·
Los mantenedores suelen responder en 11 días