ChunkSizeLimit not honoured when change in 'edit config'

[keiranmraine]

We regularly set chunkSizeLimit appropriately on BAM tracks with no problems but I've recently discovered that changing the value via the track menu and 'edit config' doesn't seem have an effect.

I noticed this when loading a track via file-open, I then tested on a pre-configured track reducing the chunkSizeLimit down as far as 10 finding that the track did not result in the expected rendering warnings about chunkSizeLimit.

Setting the value via the 'edit config' menu in the load track dialog is also not honoured.

I don't believe this is related to an error in the estimation. The figure displayed is 27MB which is the size of the BAM file which I know to have all reads in a window of ~6kb so not surprising that they are all within a single index bin.

[cmdcolin]

It is true that config parameters meant for the "storeClass" will not be honored when opening a file locally like this, it basically applies that edit config to the "track" config and not the "store" config

Are you on the latest version? The latest version added the stats timeout which was intended to fix things like #540 but maybe didn't handle local files well.