Can you be more specific about the failure? There have been issues
where CONFIG_REALTIME_ONLY was missing some features
(
https://bugs.chromium.org/p/aomedia/issues/detail?id=3077) but they
were generally found and fixed quickly. It may be best to file a bug
on that tracker:
https://bugs.chromium.org/p/aomedia/issues/entry
> My question is why CONFIG_REALTIME_ONLY is turn on for WebRTC? Considering performance? Will It be fixed by turned off CONFIG_REALTIME_ONLY?
As a build-time option CONFIG_REALTIME_ONLY generally has more to do
with library size considerations. You should be able to get identical
results with it disabled as long as you set the encoding parameters
the same.