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
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
Tags: patch
Sorry for disturbing all of you, but the tag of this report didn't
become change. I'm not sure why.
This mail is the last trial sending command tag + patch. In this time,
I attach my patch (derived from Eloston's patch), which is the same as
I posted on 8th Jan.
Takahide Nojima
On S
tag 945920 + patch
thanks
tags 945920 + patch
thanks
Hi Maintainer,
I forgot to add tag of patch, then I added.
Additionally, I've been testing chromium 79.0.3945.79 which applied
Eloston's patch, it is still quite stable, no crash.
Takahide Nojima.
On Wed, 08 Jan 2020 02:28:51 +0900 nozzy123no...@gmail.com wrote:
>
Hi Maintainer,
A few days ago, I built chromium according to the way of Eloston's,
too. But I also needed to slightly modify Eloston's patch to finish to
compile whole chromium source. I attached my version of the patch to
this report.
Until now, I'm testing this version of chromium by usual br
> I'm not at all sure if this is the right way to do it, but I was able to
> build using the enable-tracing.patch from Eloston by commenting out the
> public_configs lines containing zlib_config in
> third_party/perfetto/gn/BUILD.gn
But why not package the new version, which probably already co
I'm not at all sure if this is the right way to do it, but I was able to
build using the enable-tracing.patch from Eloston by commenting out the
public_configs lines containing zlib_config in
third_party/perfetto/gn/BUILD.gn
Right now I am typing into my webmail client using Chromium from t
Hi all,
I have tried building chromium after applying
[tracing.patch](https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=945920;filename=enable-tracing.patch;msg=14)
Unfortunately, it failed early in the build process with the following
error:
ERROR Unresolved dependencies.
//third_party/p
Hi,
This is also occurring on two machines for me. The crashes are random
but will happen after about 10 minutes of use, quite annoying...
Thanks!
Chris
On Tue, 31 Dec 2019 18:27:13 +0100 (CET) Thorsten Bonow
wrote:
> On Mon, 30 Dec 2019 13:50:36 -0800 Eloston
> wrote:
>
> [...]
>
> > $ ./debia
On Mon, 30 Dec 2019 13:50:36 -0800 Eloston
wrote:
[...]
$ ./debian/rules get-orig-source
Hi,
this fails for me:
[...]
test ! -e debian || rm -rf debian
cp -r ../debian ./
cp: cannot stat '../debian': No such file or directory
make: *** [debian/rules:212: get-orig-source] Error 1
./debian/
Alright, here's a revised process to compile Chromium locally with tracing re-
enabled:
1. First, download the patch and save it as "enable-tracing.patch"
2. Run the following:
$ wget
https://salsa.debian.org/chromium-team/chromium/-/archive/c88b97a6dc183a6a7f8a05aee9e99957285a9371/chromium-c88b9
Hi Eloston,
Thanks for figuring out the cause of these random crashes! However, I was
unable to recompile chromium from source following your instructions. I got
the following error message at step 4b:
jj@telos:~/src/chromium-79.0.3945.79$ debian/rules get-orig-source
wget -nv --show-pro
Hey all,
I highly suspect all of these crashes are due to disable/tracing.patch:
https://salsa.debian.org/chromium-team/chromium/blob/3bcbf4a32166e394c45caf66e1348127284f9094/debian/patches/disable/tracing.patch
Two reasons:
* It is the only patch that makes changes to memory_instrumentation.
*
Hello,
Been running Chromium for the last 6 hours now, no crash since, so it
looks like that last patch finally got it.
- Michel
Hi,
On Fri, 27 Dec 2019 15:31:13 +0100 Jaap Joris Vens wrote:
> On Fri, Dec 27, 2019 at 01:29:13PM +0100, Stefan Bühler wrote:
> >Hi,
> >
> >yes, you are right, my patch only fixes the task manager crash.
> >
> >I now took a look at all backtraces, and all apart the first one
> >(probably older v
On Fri, Dec 27, 2019 at 01:29:13PM +0100, Stefan Bühler wrote:
Hi,
yes, you are right, my patch only fixes the task manager crash.
I now took a look at all backtraces, and all apart the first one
(probably older version?) seem to be the same "other" instance:
--- 8< ---
I am not quite follow
Hi,
yes, you are right, my patch only fixes the task manager crash.
I now took a look at all backtraces, and all apart the first one
(probably older version?) seem to be the same "other" instance:
---
#0 0x5a77cee7 in
memory_instrumentation::MemoryInstrumentation::RequestGlobalDump(st
Hello,
Same here unfortunately. It has fixed the SIGSEGV when opening the Task
Manager, but as feared, that crash seems to be separate from the
randomly occurring one.
- Michel
19 matches
Mail list logo
