Thank you so much Even. It is working like a charm!
-Original Message-
From: Even Rouault [mailto:even.roua...@spatialys.com]
Sent: 30 September, 2016 01:05
To: gdal-dev@lists.osgeo.org
Cc: Francisco Javier Calzado
Subject: Re: [gdal-dev] Multithread deadlock
> I don't think th
> I don't think this comes from GDALPam, but rather from the lower level
> machinery of GDALRasterBand & GDALRasterBlock. As I said before, multi-
> threaded writing has never properly worked and I'm not sure if the issue
> you see is just an implementation bug or a design bug.
OK, after investiga
Francisco,
> Bingo! I've just tested with an ENVI dataset and is failing, same issue
> with a few random blocks missing in the resulting rasters. Find below a
> link with the code for a simple test reproducing the issue (also included
> the ENVI dataset used). Just bear in mind that sometimes may
Cache() on dataset destructor.
-Original Message-
From: Even Rouault [mailto:even.roua...@spatialys.com]
Sent: 27 September, 2016 19:16
To: Francisco Javier Calzado
Cc: gdal-dev@lists.osgeo.org
Subject: Re: [gdal-dev] Multithread deadlock
Le mardi 27 septembre 2016 16:35:26, Francisco Javi
Le mardi 27 septembre 2016 16:35:26, Francisco Javier Calzado a écrit :
> Hi Even,
>
> Your changes have fixed the issue with multiple threads, now they can write
> simultaneously without getting locked. I've done some test in GTiff format
> and everything went OK.
Did you try with other drivers
Thanks,
BR. Javier.
-Original Message-
From: gdal-dev [mailto:gdal-dev-boun...@lists.osgeo.org] On Behalf Of Francisco
Javier Calzado
Sent: 27 September, 2016 09:50
To: Even Rouault ; gdal-dev@lists.osgeo.org
Subject: Re: [gdal-dev]
l-dev@lists.osgeo.org
Cc: Francisco Javier Calzado ; Andrew
Bell
Subject: Re: [gdal-dev] Multithread deadlock
Hi,
I admire Andrew's enthousiasm and would happily let him tackle the next bug
reported in this area ;-)
I could reproduce the deadlock with the same stack trace and have pushed a fix
01.dll!GDALClose(void * hDS) Line 2998 C++
>
> > Test.exe!main::__l2::(std::basic_string > r_traits,std::allocator > sourcefilePath,
> > std::basic_string,std::allocator
> > > targetFilePath, int threadID) Line 66
ourcefilePath,
> std::basic_string,std::allocator >
> targetFilePath, int threadID) Line 66 C++
From: Andrew Bell [mailto:andrew.bell...@gmail.com]
Sent: 26 September, 2016 16:06
To: Francisco Javier Calzado
Cc: gdal-dev@lists.osgeo.org
Subject: Re: [gdal-dev] Multithread dead
Deadlocks are usually easy to debug if you can get a traceback when
deadlocked. If you can attach with gdb (or run in the debugger) and
reproduce and post the stack at the time ('where' from gdb), it should be
no problem to fix. Trying to reproduce on different hardware can be
difficult.
On Mon,
Hi guys,
I am experiencing a deadlock with just 2 threads in a single reader & multiple
writer scenario. This is, threads read from the same input file (using
different handlers) and then write different output files. Deadlock comes when
the block cache gets filled. The situation is the followi
11 matches
Mail list logo
