Le lundi 18 mars 2013 10:26:44, Andrea Aime a écrit : > On Mon, Mar 18, 2013 at 7:34 AM, cmaul <[email protected]>wrote: > > Because the tiles are cut from ecw there are a lot of components > > involved. Where could I find an indicator of what it is that's making > > the JVM collapse?
The ECW SDK can consume a lot of RAM (and there was a bug in old SDK 3.3 where in some configurations, the 1/4 RAM threshold was not respected). You should look at the ECW_CACHE_MAXMEM configuration option / environement variable documented in http://gdal.org/frmt_ecw.html > > Welcome to the wondering world of native code integration... a minor glitch > in GDAL or the ECW is enough to take down the entire JVM, there is no > protection against SEGFAULT errors in native code. > > That said, I'm not sure how to help... maybe it's the specific ECW version, > I believe GDAL is supposed to be built against version 3.x... but I also > may be quite off the mark. > > On the bright side GDAL is working on a plan to have these readers work > in a separate process, in order to proctect itself from such catastrophic > failures. > But I don't know if/when that will be available, you might want to check on > the > GDAL mailing list. GDAL 1.10 to be released in a couple of weeks : http://gdal.org/gdal_api_proxy.html > > Cheers > Andre ------------------------------------------------------------------------------ Own the Future-Intel(R) Level Up Game Demo Contest 2013 Rise to greatness in Intel's independent game demo contest. Compete for recognition, cash, and the chance to get your game on Steam. $5K grand prize plus 10 genre and skill prizes. Submit your demo by 6/6/13. http://altfarm.mediaplex.com/ad/ck/12124-176961-30367-2 _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
