Hi, > A backtrace that includes chromium's debugging symbols would be more > helpful than the "me too" messages.
How about stack traces from a first message? Are they useless? If you want full backtrace from gdb then describe how to get if, because usual approach (gdb <program> --> run --> segfault --> bt full) will not work with chromium as far as I understand. Or you may easily install 32-bit chromium in your 64-bit system and reproduce segfaults by yourself. > The biggest difference from deb8u1 is embedded instead of system > ffmpeg. It would be useful to know whether building with the embedded > library fixes it (just unapply ffmpeg.patch). I have built chromium/51.0.2704.79-1.1 without this patch and all works fine. So the root of problem is exactly here. But please do not ask to test any patches, because in my system this package was building during 8.5 hours and all this time my laptop was too hot and I was worrying it will be overheated. Best wishes, Boris