There's nothing better than spending 30min tracking a bug that crashes ffmpeg on your system and finding a bug filed 2 years ago where devs ignore the issue saying that even though it's against the specs it's never a problem in real life. https://trac.ffmpeg.org/ticket/6403
-
-
Like hey, that new hardening tool is telling us the code we ship to billion of devices is shit. Can you make it shut up please?
Show this threadThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
“No real world examples that this badly designed code causes a problem so lets close that bug” is just an acknowledgement that piling up technical debt is fine. Lazy and irresponsible. Re-closing it after getting an example and blaming the hardening tool? Madness.
-
That kind of behavior always makes me wonder what other kind of horrors are lurking in the codebase. When your values allow these “features” into the code, you are bound to encounter a lot of them. I can only assume adding ffmpeg to an app opens a huge security risk.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.