10525 2016-10-28 15:07:17 +0000 Chromium 52 segfaults on i.MX6 duallite 2019-01-31 19:08:09 +0000 1 1 7 Build System, Metadata & Runtime BSPs bsps-meta-fsl-arm unspecified x86 Multiple RESOLVED WONTFIX Medium normal Future 1 ernstp otavio otavio --- Regression (Used to work) No (bug/feature does not impact docs) oldest_to_newest 67726 0 ernstp 2016-10-28 15:07:17 +0000 Hi, I'm running on a custom arm board with i.MX6 duallite. I tried upgrading from Chromium 48 (which works very well) to 52. However it segfaults: /usr/bin/google-chrome: line 11: 1561 Segmentation fault /usr/bin/chromium/chrome ${CHROME_EXTRA_ARGS} $@ I see an empty window flash on screen before the crash, no actual content is drawn. I tried removing --ignore-gpu-blacklist and also some other flags like --in-process-gpu and --no-sandbox but I got an identical crash no matter. Where to start debugging.. ? 67729 1 ernstp 2016-10-28 15:28:29 +0000 Here's a backtrace without debug symbols. I ran with --use-gl=egl --gpu-no-context-lost --ignore-gpu-blacklist --user-data-dir=/var/volatile/roothome/.chromium/ --single-process --in-process-gpu --no-sandbox --no-zygote --disable-gpu to try to minimize the number of processes involved... (gdb) bt #0 0x76036094 in ?? () from /usr/lib/libstdc++.so.6 #1 0x557e54c0 in std::_Rb_tree_iterator<std::pair<unsigned long long const, int> > std::_Rb_tree<unsigned long long, std::pair<unsigned long long const, int>, std::_Select1st<std::pair<unsigned long long const, int> >, std::less<unsigned long long>, std::allocator<std::pair<unsigned long long const, int> > >::_M_emplace_hint_unique<std::piecewise_construct_t const&, std::tuple<unsigned long long const&>, std::tuple<> >(std::_Rb_tree_const_iterator<std::pair<unsigned long long const, int> >, std::piecewise_construct_t const&, std::tuple<unsigned long long const&>&&, std::tuple<>&&) () #2 0x573436c4 in ?? () #3 0x57347aba in ?? () #4 0x55044816 in ?? () #5 0x553d4c6a in ?? () #6 0x553d4c6a in ?? () #7 0x55445118 in ?? () #8 0x55445400 in ?? () #9 0x55445478 in ?? () #10 0x55445b6e in ?? () #11 0x554432ca in ?? () #12 0x553df2a6 in ?? () #13 0x553deba8 in ?? () #14 0x553dec84 in ?? () #15 0x553d921a in ?? () #16 0x56ead69c in ?? () #17 0x570dccb0 in ?? () #18 0x570dde7a in ?? () #19 0x551c66c0 in ?? () #20 0x551960e6 in ?? () #21 0x55196798 in ?? () #22 0x55196928 in ?? () #23 0x5517c7d0 in ?? () #24 0x551a6002 in ?? () #25 0x5519579c in ?? () #26 0x56e3c298 in ?? () #27 0x56e3c7c6 in ?? () #28 0x551b5664 in ?? () #29 0x551b3092 in ?? () #30 0x76c86f00 in ?? () from /lib/libpthread.so.0 Backtrace stopped: previous frame identical to this frame (corrupt stack?) 72038 2 otavio 2017-04-03 19:01:31 +0000 This is indeed a BSP specific thing. We just merged an upgrade for Chromium 54 in master and would be good to give it a new try. The bug report is lacking some information as for example what is the backend in use? is it X11 or Wayland? 72532 3 ernstp 2017-04-17 15:39:11 +0000 This was with X11. I don't have hardware to verify this anymore. 82927 4 sjolley.yp.pm 2019-01-31 19:08:09 +0000 bsps-meta-fsl-arm issues are now tracked in GitHub. Please see: https://github.com/Freescale/meta-freescale