Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

gdalwarp error "Failed to acquire WarpMutex in WarpRegion()" #3631

Closed
maphew opened this issue Mar 31, 2021 · 0 comments · Fixed by #3788
Closed

gdalwarp error "Failed to acquire WarpMutex in WarpRegion()" #3631

maphew opened this issue Mar 31, 2021 · 0 comments · Fixed by #3788
Milestone

Comments

@maphew
Copy link
Contributor

maphew commented Mar 31, 2021

Expected behavior and actual behavior.

ERROR 1: Failed to acquire WarpMutex in WarpRegion() on source single channel 16bit image of size 93723, 33409.

gdalinfo on source: tri_mergedDEM_clipped_16bit.tif.txt

Steps to reproduce the problem.

gdalwarp --config GDAL_CACHEMAX 4096 -wm 512 -multi -co TILED=YES ^
-co COMPRESS=ZSTD -t_srs EPSG:3579 -r mode -co predictor=2  ^
 IN.tif  OUT.tif

Operating system

Windows 10 Enterprise, Version 10.0.19041 Build 19041

GDAL version and provenance

GDAL 3.1.4, released 2020/10/20 via Qgis v3.16.

Analysis

I see that in the -multi mode, the I/O threads waits for a maximum of 10 minutes for the computation thread to have finished. And you likely hit that limit because of the large value of -wm you set. There's no reason we max at 10 minutes however.

From thread http://osgeo-org.1560.x6.nabble.com/gdal-dev-More-info-on-gdalwarp-resampling-methods-tp5484028p5484100.html

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants