Good Build:68.0.3415.0(Revision: 554688)
Bad Build: 68.0.3417.0(Revision: 555217)

ChangeLog info:
https://chromium.googlesource.com/chromium/src/+log/68.0.3415.0..68.0.3417.0?pretty=fuller&n=10000

Suspect: r555214 ?

@mattm: Could you please help to reassign this issue if your change is not cause for it.

Note: 
1.Unable to provide bisect using narrow bisect and bisect per revision as getting all good build, hence providing suspect from change log.
2.Issue is not seen on Windows(7,8,8.0,10) and Mac(10.12.6,10.13.1,10.13.5)
3.Please refer actual screencast for the issue from (https://drive.google.com/open?id=1axpYohXDDx_-HxrHCb6eD34Xg92q64qw) link.

Deleted: Expected_PDF.webm 928 KB

	Expected_PDF.webm 928 KB View Download

providing few more crash IDs: 866e4acf99a61a68, 79a866d646861220 , b28a8ee4a56493ee and URLs: http://unec.edu.az/application/uploads/2014/12/pdf-sample.pdf
https://s1.q4cdn.com/806093406/files/doc_downloads/test.pdf

adding RBD, please change if required.

Note: 
1. Unable to attach stacktrace, not enough stack trace is available (might be Issue 838858)
2. Unable to reproduce on corp network using Debian OS. Requesting MTV team to check and update accordingly.

Not sure why this was assigned to me, I don't have anything to do with the suspect CL. (Maybe a copy-paste error since my CL was right after that in the changelog? My CL is unrelated and test-only anyway.)

This does not repro for me on 68.0.3418.0 (Developer Build) (64-bit). None of the stacks have any kind of backtrace information, I also don't see URLs, so it's hard to say if this is caused by PDFium.

hnakashima@ the blamed roll is your CL which shouldn't effect this code, but can you try to repo and see what happens?

To which of the rolls did you trace this?

Per comment #1 https://chromium.googlesource.com/chromium/src/+/6c17168f8eb19826cab3f9b882d46c6070aa347b

Unable to reproduce here.

Can you please provide the stack trace? We can't repro the bug, so we need more information to look into this.

ligimole@ - are you able to recreate this issue?

Unfortunately there is no information in the crash ids mentioned in #0 and #2 reports are not symbolized.

Crash Report
=============
Thread 0 (id: 1300) CRASHED [SIGILL @ 0x00007ff0a38f4f3e ]
Stack Quality0%Show frame trust levels
0x00007ff0a38f4f3e	(chrome + 0x05c84f3e )	
0x00007ff0a38f4e48	(chrome + 0x05c84e48 )	
0x00007ff0a38e098c	(chrome + 0x05c7098c )	
0x00007ff0a1186b70	(chrome + 0x03516b70 )	
0x00007ff0a11868f7	(chrome + 0x035168f7 )	
0x00007ff0a008b85d	(chrome + 0x0241b85d )	
0x00007ff09fedabdf	(chrome + 0x0226abdf )	
0x00007ff09fedb4ec	(chrome + 0x0226b4ec )	
0x00007ff09fed956a	(chrome + 0x0226956a )	
0x00007ff0a008bb8a	(chrome + 0x0241bb8a )	
0x00007ff0a0092edf	(chrome + 0x02422edf )	
0x00007ff0a009328f	(chrome + 0x0242328f )	
0x00007ff0a1407655	(chrome + 0x03797655 )	
0x00007ff0a142062a	(chrome + 0x037b062a )	
0x00007ff0a1420c64	(chrome + 0x037b0c64 )	
0x00007ff0a1423b0d	(chrome + 0x037b3b0d )	
0x00007ff09b772e03	(libglib-2.0.so.0.4002.0 + 0x00048e03 )	
0x00007ff09b781b3f	(libglib-2.0.so.0.4002.0 + 0x00057b3f )	
0x00007ff09b773047	(libglib-2.0.so.0.4002.0 + 0x00049047 )	
0x00007ff09b7730eb	(libglib-2.0.so.0.4002.0 + 0x000490eb )	
0x00007ff0a1423902	(chrome + 0x037b3902 )	
0x00007ff0a1442583	(chrome + 0x037d2583 )	
0x00007ff0a1145c52	(chrome + 0x034d5c52 )	
0x00007ff0a146d6db	(chrome + 0x037fd6db )	
0x00007ff09dd92933	(chrome + 0x00122933 )	
0x00007ff0a1483d3f	(chrome + 0x03813d3f )	
0x00007ff09ffc4690	(chrome + 0x02354690 )	
0x00007ff0a55e2e7b	(chrome + 0x07972e7b )	
0x00007ff09f553307	(chrome + 0x018e3307 )	
0x00007ff09f5532e7	(chrome + 0x018e32e7 )	
0x00007ff09ffc6721	(chrome + 0x02356721 )	
0x00007ff09ffbfe95	(chrome + 0x0234fe95 )	
0x00007ff09f5e9b0c	(chrome + 0x01979b0c )	
0x00007ff0a1120b9b	(chrome + 0x034b0b9b )	
0x00007ff0a112ae03	(chrome + 0x034bae03 )	
0x00007ff09df38404	(chrome + 0x002c8404 )	
0x00007ff09da5503b	(ld-2.19.so + 0x0000a03b )	
0x00007ff09e417a7f	(chrome + 0x007a7a7f )	
0x00007ff0a55e2e7b	(chrome + 0x07972e7b )	
0x00007ff09f553307	(chrome + 0x018e3307 )	
0x00007ff09f5532e7	(chrome + 0x018e32e7 )	
0x00007ff09f593467	(chrome + 0x01923467 )	
0x00007ff0a14a2dd9	(chrome + 0x03832dd9 )	
0x00007ff0a55e2e7b	(chrome + 0x07972e7b )	
0x00007ff09f553307	(chrome + 0x018e3307 )	
0x00007ff09f5532e7	(chrome + 0x018e32e7 )	
0x00007ff09f593467	(chrome + 0x01923467 )	
0x00007ff0a55e2e7b	(chrome + 0x07972e7b )	
0x00007ff09f553307	(chrome + 0x018e3307 )	
0x00007ff09f5532e7	(chrome + 0x018e32e7 )	
0x00007ff09f593467	(chrome + 0x01923467 )	
0x00007ff0a14a2dd9	(chrome + 0x03832dd9 )	
0x00007ff09f458fff	(chrome + 0x017e8fff )	
0x00007ff0a111fc3f	(chrome + 0x034afc3f )	
0x00007ff09f458fff	(chrome + 0x017e8fff )	
0x00007ff0a111e9c3	(chrome + 0x034ae9c3 )	
0x00007ff09f5e8aa2	(chrome + 0x01978aa2 )	
0x00007ff097bb3f44	(libc-2.19.so + 0x00021f44 )	
0x00007ff09f55eef7	(chrome + 0x018eeef7 )	
0x00007ff09f458fff	(chrome + 0x017e8fff )	
0x00007ff09da5b3c2	(ld-2.19.so + 0x000103c2 )	
0x00007ff09f458fff	(chrome + 0x017e8fff )	
0x00007ff09f459029	(chrome + 0x017e9029 )	

dbote@ can you try with a fresh profile and let us know whether the browser is still crashing.

Keeping an RB label for tracking purpose.

With respect to comment 10:

Retested above crash issue with fresh profile and it is reproducing on latest build #68.0.3417.2 and #68.0.3418.0 

Kindly refer attached screen cast from the (https://drive.google.com/open?id=1hKq9rVtGDBSfKq5dxj_kOdFB0CAS4mBW) drive link.

Thank you.

Can you try a per revision bisect.

SIGILL means it's probably due to r554828 which is being reverted in https://chromium-review.googlesource.com/1042765

However, with a local test build I've been unable to reproduce this failure. Is the build of chrome for the stack trace above a local build or is it available somewhere for me to take a look at?

The stack trace is from chrome builds reported from crash server. go/crash/79a866d646861220

 Issue 839327  has been merged into this issue.

Thanks for the revert.

We are seeing multiple crashes on linux due the this regression, hence tagging as RBD for tracking purpose.

 Issue 839362  has been merged into this issue.

For posterity, the reason the crash didn't reproduce was because it was in Unity-specific code.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/12f5c3bf9d441834d3cbd16ed4ed1a0214cc3d91

commit 12f5c3bf9d441834d3cbd16ed4ed1a0214cc3d91
Author: Vlad Tsyrklevich <vtsyrklevich@chromium.org>
Date: Thu May 03 23:59:35 2018

CFI-icall: Blacklist dynamically resolved cross-DSO calls for Unity

BUG= 839362 , 838785 

Change-Id: I09528458d875c93e7c821c7789fc013f3f836b0a
Reviewed-on: https://chromium-review.googlesource.com/1043283
Reviewed-by: Peter Collingbourne <pcc@chromium.org>
Commit-Queue: Peter Collingbourne <pcc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555913}
[modify] https://crrev.com/12f5c3bf9d441834d3cbd16ed4ed1a0214cc3d91/tools/cfi/blacklist.txt

Update:

Above crash issue is fixed on latest builds #68.0.3418.2 and #68.0.3419.0.

Kindly refer screencast from (https://drive.google.com/file/d/1W3kA2JZyS8Uw-nT4dUpcGmbEpZH8VUxZ/view?usp=drivesdk) drive link.

Thank you.