Hi all, The status so far is that we have a patch that solves the problem by re-enabling [tracing][1], but the reason that tracing was disabled in the first place is because it depends on minified javascript. You can recompile chromium yourself but this is not a permanent solution.
It seems that nobody has started the effort of trying to write a new patch that removes the tracing functionality from the upstream source code, or to find the bug and fix the way it's removed now. Dear maintainer, could you please chime in and let us know how we could help? Greetings, JJ [1]: https://www.chromium.org/developers/how-tos/trace-event-profiling-tool On Mon, Jan 13, 2020 at 09:52:36AM -0500, Джонатан Вашингтон wrote:
Dear package maintainer(s), In case it is useful information, this issue affects me as well, and has for several weeks. Chromium is usable for only a few minutes before it crashes with a backtrace almost identical to those already shared. It does not seem to matter how many or what kind of pages are open, or whether the browser is actively being used / receiving window manager focus or not. Please let me know if there is anything I can do to help identify the problem or test a fix. -- Jonathan -- To unsubscribe, send mail to 945920-unsubscr...@bugs.debian.org.
