We're using IJG libjpeg on CrOS for decoding of user-controlled images that are displayed to all users on the login screen. The argument for this was that IJG libjpeg was more robust (significantly fewer security bugs) than libjpeg-turbo. However, new versions of IJG libjpeg have an incompatible API so we're essentially stuck at version 6b. That means that the tradeoff might not be as generous for IJG libjpeg anymore. Consider reviewing the state of both codebases and simplifying CrOS code by removing IJG libjpeg.