Open the page in an Incognito window... same problem.

Unable to reproduce the issue on Debian Rodete with chrome #69.0.3497.92 and didn't observed any crash.

jidanni@ Could you please help us with 16 digit crash id from chrome://crashes

Deleted: Crash.png 15.1 KB

	Crash.png 15.1 KB View Download

chrome://crashes says
Crashes
Crash reporting is disabled.
Crash reporting is not available in Chromium.

Crashes (0)
You have no recently reported crashes. Crashes that occurred when crash reporting was disabled will not appear here.

So sorry.

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

And even my attempts in https://bugs.chromium.org/p/chromium/issues/detail?id=888482 did not turn it on.

As https://stackoverflow.com/a/48489046/1118719 says
"Enabling crash reporting on Chromium is not possible,"
So I'm sorry. I cannot help you.

Can you provide a symbolized stack trace. You'll have to do that with the symbols from whereever you got your Chromium from.

For ubuntu see:
https://wiki.ubuntu.com/Chromium/Debugging

For debian see:
https://wiki.debian.org/Chromium/Debugging

Thanks but as you see on https://wiki.debian.org/Chromium/Debugging?action=info
I had to cross out the invalid information there long ago.
As far as the correct method... well maybe one day somebody will add it.

Anyway maybe one day it will be easier for me to help you. But until then I think I should just accept the crashes and just view the pages with another browser.

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Tested this issue on Debian rodete using chromium#69.0.3497.0 and unable to reproduce this issue.

Attaching screen-cast for reference.

@Reporter: Could you please look into screencast and let us know if anything is missed from your end. Also please try this on fresh profile with no apps or extensions or flags enabled and let us know the behavior.

Thanks!

Deleted: Sep 25 2018 12_28 PM.webm 20.5 MB

Sep 25 2018 12_28 PM.webm 20.5 MB Download

OK viewing the page on a fresh Linux account works fine.
Then why didn't it work on my usual account in an incognito window?
Ah, Adblock Plus was still on there.
Turning Adblock Plus off for that site... and the page loads fine.
OK so Adblock Plus caused the crash. Hmmm.
Well at least I have a new idea out of this:
https://bugs.chromium.org/p/chromium/issues/detail?id=889897

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

jidanni@,
Can we close this issue as per c#11?Please confirm.
Thanks..!

OK. Close it. Made https://issues.adblockplus.org/ticket/7028 .

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

As per comment #15, Closing this issue

Please could you reopen this issue? I can reproduce it reliably with the attached extension which blocks one request to https://imasdk.googleapis.com/js/sdkloader/ima3.js using the chrome.webRequest.onBeforeRequest API.

For reference I am running Debian testing, I have installed Chromium with `apt install chromium`, I'm running version "Version 69.0.3497.92 (Developer Build) built on Debian buster/sid, running on Debian buster/sid (64-bit)".

When I launch Chromium with the --single-process argument I can no longer reproduce the problem.

When the tab crashes the following shows up in the terminal I launched the browser from:

libpng warning: iCCP: Not recognizing known sRGB profile that has been edited
Received signal 11 SEGV_MAPERR 000000000000
#0 0x5563e722ee4e <unknown>
#1 0x5563e722f24b <unknown>
#2 0x5563e722f8ce <unknown>
#3 0x7f767b1508e0 <unknown>
#4 0x5563e9b924e7 <unknown>
#5 0x5563e9ba6619 <unknown>
#6 0x5563e68b4ff2 <unknown>
#7 0x5563e69bbf61 <unknown>
#8 0x5563e6d2642e <unknown>
  r8: 00005563e9ba6899  r9: 00005563ee853840 r10: 00005563edfcf5c0 r11: 00007f7671eb9c40
 r12: 0000000000000000 r13: 00007ffeae788580 r14: 00007ffeae788590 r15: 00007ffeae788568
  di: 00007ffeae788590  si: 00005563ea8b3ce0  bp: 00007ffeae788780  bx: 00001a859ce47d50
  dx: 00005563e9b924dc  ax: 0000000000000000  cx: 00000000000000e1  sp: 00007ffeae788540
  ip: 00005563e9b924e7 efl: 0000000000010206 cgf: 002b000000000033 erf: 0000000000000004
 trp: 000000000000000e msk: 0000000000000000 cr2: 0000000000000000
[end of stack trace]
Calling _exit(1). Core file will not be generated.

Thanks, Dave.

Deleted: 886921-demo.zip 879 bytes

886921-demo.zip 879 bytes Download

Chromium team: please reopen the issue.

We need a stack trace. I've tried to reproduce this against my own build of Chromium with the extension provided and cannot. It must be something that the debian build is doing. Unfortunately since we didn't build it we don't have symbols. 

Adding thomasanderson@ perhaps he knows how to get symbols on debian since the documentation seems out of date these days.

I think he needs to use https://packages.debian.org/jessie/chromium-dbg .

But that is way older than https://packages.debian.org/sid/chromium .

https://wiki.debian.org/Chromium/Debugging is out of date.

Yea, I took a look for chromium-dbg or a similar package but unfortunately didn't have much luck. Furthermore, I could no longer even reproduce the problem when following those instructions since it seemed to enable --single-process.

Often I hear here to get a bug reopened one needs to open a new bug.

I've reached out to the debian maintainer to ask why the debug symbols are not up to date and to ask the wiki page be corrected. A new open bug wouldn't get us anywhere if we don't have a stack trace. I suggest you ask on a debian mailing list about this. Since the chromium project didn't build or distribute the software it needs to be the maintainer of the software that first looks at the issue since it doesn't reproduce in Chrome.

Well I filed https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910842 to get the maintainer to allow https://bugs.chromium.org/p/chromium/issues/detail?id=886921#c18 ABP staff to give you a stack trace.

Now on Debian in chromium 70.0.3538.54-1
/usr/share/doc/chromium/README.Debian
has working instructions on how to get a stack trace.

Cool, that seems to work, but annoyingly I can't reproduce the crash when debugging Chromium! Can you?

Seems to not crash anymore in 
chromium:
  Installed: 70.0.3538.54-2