Opened 17 years ago
Closed 17 years ago
#100 closed defect (fixed)
GDAL access not threadsafe
| Reported by: | warmerdam | Owned by: | gregboone |
|---|---|---|---|
| Priority: | major | Milestone: | 3.3.0 |
| Component: | GDAL Provider | Version: | 3.2.0 |
| Severity: | 3 | Keywords: | threading |
| Cc: | jbirch, haris | External ID: |
Description
The FDO GDAL Provider is not threadsafe within GDAL. In particular, it is not legal for multiple threads to access a single GDALDatasetH at the same time. This causes intermittent crashes and other dangerous behavior under heavy load, such as when generating tiles with mapguide.
Change History (6)
comment:1 by , 17 years ago
| Cc: | added |
|---|---|
| Status: | new → assigned |
comment:2 by , 17 years ago
| Owner: | changed from to |
|---|---|
| Status: | assigned → new |
comment:3 by , 17 years ago
| Status: | new → assigned |
|---|
comment:6 by , 17 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Note:
See TracTickets
for help on using tickets.
I have committed a preliminary "big lock" attempt in the fdogdal 3.2.x branch (r127).