RAM parameter application not used to define the streaming size with extended options streaming:type=stripped

Description

Bug happens with a specific use of extended filename for application launch :

Ram parameter is not used to define the streaming size when the streaming mode stripped is chosen by the user thanks to extended filename.

Two warnings from ImageFileWriter are triggered :

• Streaming configuration through extended filename is used. Any previous streaming configuration (ram value, streaming mode ...) will be ignored.
• sizemode is auto but sizevalue is 0. Value will be fetched from configuration file if any, or from cmake configuration otherwise.

With stripped as streaming mode and a size value equal to 0, ImageFileWriter instanciate an RAMDrivenStrippedStreamingManager with availableRAM to 0. StreamingManager class replaces availableRAM by 10241024ConfigurationManager::GetMaxRAMHint(). Ram parameter is never used in this case.

Steps to reproduce

Launch an application with extended filename (stripped as streaming mode) for output image name. The following name is an example of extended filename with stripped mode and no size value defined :

name.tiff?&streaming:type=stripped

/label bug

Configuration information

OS : Centos

OTB version : 6.5