omp_pause_resource() warning on every SparseArray.Call() with the clang/libomp toolchain (Windows arm64)
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 3/5
- Geschätzter Aufwand
- 1-2 Tage
- Anfängerfreundlichkeit
- 35/100
Rechercherichtung
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.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
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).
- Vorherrschende Sprache
- C
- Sterne
- 13
- Forks
- 3
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Entwicklungsumgebung
Dieses Projekt bietet weder Dev-Container noch Dockerfile noch Beitragsleitfaden – die Einrichtung liegt bei Ihnen. Beginnen Sie mit der README; die allgemeinen Schritte stehen in unserem Leitfaden für den ersten Beitrag.
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus Bioconductor/SparseArray
-
Schwierigkeit 5/5 Über eine Woche Anfängerfreundlichkeit 35/100
Bioconductor/SparseArray#20 · 3 Kommentare ·
-
enhancement
Schwierigkeit 5/5 Über eine Woche Anfängerfreundlichkeit 25/100
Bioconductor/SparseArray#5 · 7 Kommentare · 1 Reaktion ·
Alle Issues in Bioconductor/SparseArray
Ähnliche Issues
-
bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 84/100
Maintainer antworten meist innerhalb von 1 Tag
-
enhancement
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 68/100
ChupathingyCE/chupathingyce#1550 ·
Maintainer antworten meist innerhalb von 1 Tag
-
[BUG] SWAPDB sends no invalidation to CLIENT TRACKING clientsEvtl. vergeben Ein verknüpfter Pull Request ist offen oder bereits gemergt. Offen
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 83/100
redis/redis#16302 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
-
slice
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 73/100
Life-Framework/Life-Framework#3878 ·
Maintainer antworten meist innerhalb von 1 Tag
-
`sha256()` returns a wrong hash when libsql-ffi is built with gcc 11 or laterEvtl. vergeben @colinhacks hat das heute übernommen. Offen
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
tursodatabase/libsql#2333 ·
Maintainer antworten meist innerhalb von 11 Tagen