Opened 9 years ago
Closed 9 years ago
#6149 closed defect (fixed)
Destructor of GML data source does not flush non seekable output file
| Reported by: | Ari Jolma | Owned by: | warmerdam |
|---|---|---|---|
| Priority: | normal | Milestone: | 1.11.4 |
| Component: | default | Version: | unspecified |
| Severity: | normal | Keywords: | |
| Cc: |
Description
ogrgmldatasource.cpp:144 calls VSIFCloseL for the output. However, VSIFCloseL does not flush the file. Thus, even though the GML data source object may be gone, its output may still be pending. This is a problem for example in the web environment, where one needs control over output.
In my case I'm using /vsistdout/. Maybe Flush() should be called in the Close method of VSIStdoutHandle if not in VSIFCloseL.
Change History (1)
comment:1 by , 9 years ago
| Milestone: | → 1.11.4 |
|---|---|
| Resolution: | → fixed |
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
trunk r30995, branches/2.0 r30996, branches/1.11 r30997 "/vsistdout/: flush when closing the handle (reported and fix suggested by ajolma, #6149)"