murphy

I finally managed to somehow replicate the issue. Even though this was for sure not the case of previous crashes, this is the only way I was able to reproduce...

It is not clear what should happen next. current `Publish` to be renamed and hidden? (Legacy Publish and create settings to put it back on, or?) current `Tray Publish` renamed...

it is weird anyway `x264 [error]: malloc of size 440626798 failed ` what is the problem with 440MB?

I still have over 14GB ram available (out of 32) screengrabbed just after the failure 

Hmm it would mean x264 codec will have troubles even with 4k Interestingly Peter @kalisp was able to use 16k. How come?

Shouldn't we update our vendorized ffmpeg binary in OP? Our version is 4.4 compared to latest 5.1

and also if the max resolution of review is behaving so unpredictable, we may want to put this into settings so there is an easy way of changing it, depending...

If we only count the number of shader connections to assume there are component level assignments we are missing the case where you select ALL faces of an object and...

just tested latest develop and this bug is still there . .

@BigRoy comment in another thread > **Describe the bug** > > The Maya Validate Frame Range function has a [repair method that updates the instance `frameStart` and `frameEnd`](https://github.com/pypeclub/OpenPype/blob/develop/openpype/hosts/maya/plugins/publish/validate_frame_range.py?rgh-link-date=2022-02-04T18%3A38%3A36Z#L82-L93). However, Renderlayers...