SEGV in print dialog with #enable-site-per-process enabled
Reported by
dkde...@gmail.com,
Mar 11 2018
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.186 Safari/537.36 Steps to reproduce the problem: 1. Enable #enable-site-per-process 2. Open any page, even a blank one 3. Press CTRL-P What is the expected behavior? Print UI visible and no crash. What went wrong? I see print UI for a split second (controls on the left) then chromium crashed. Console output: Received signal 11 SEGV_MAPERR 000000000008 #0 0x555b47192b2e <unknown> #1 0x555b45384e3f <unknown> #2 0x555b47192efe <unknown> #3 0x7fea612bdd50 <unknown> #4 0x555b46434ac5 <unknown> #5 0x555b464347e3 <unknown> #6 0x555b4929eac9 <unknown> #7 0x555b4a31c16b <unknown> #8 0x555b4a31d0f6 <unknown> #9 0x555b45fd7147 <unknown> #10 0x555b45ce898b <unknown> #11 0x555b45ceb4a6 <unknown> #12 0x555b45e9d3ef <unknown> #13 0x555b478a97a4 <unknown> #14 0x555b47193fa9 <unknown> #15 0x555b471b3624 <unknown> #16 0x555b471b450c <unknown> #17 0x555b471b466a <unknown> #18 0x555b471b5ea1 <unknown> #19 0x555b471b5eed <unknown> #20 0x7fea5f1d1517 g_main_context_dispatch #21 0x7fea5f1d1780 <unknown> #22 0x7fea5f1d182c g_main_context_iteration #23 0x555b471b5c72 <unknown> #24 0x555b471dc7f9 <unknown> #25 0x555b470a6af2 <unknown> #26 0x555b45b793f1 <unknown> #27 0x555b45b7b0f5 <unknown> #28 0x555b45b73bc9 <unknown> #29 0x555b46e074c1 <unknown> #30 0x555b46e15a06 <unknown> #31 0x555b46e05e35 <unknown> #32 0x555b4539f20f ChromeMain #33 0x7fea56f5e541 __libc_start_main #34 0x555b4539f06a _start r8: 0000000000000020 r9: 0000000000000000 r10: 0000555b4f8baf38 r11: 0000555b50bf2660 r12: 00007ffc637ec028 r13: 00007ffc637ec030 r14: 0000000000000000 r15: 0000555b506b0b00 di: 0000000000000000 si: 00007ffc637ec028 bp: 00007ffc637ec0f0 bx: 00007ffc637ec060 dx: 0000555b506b0b00 ax: 0000555b50c03af0 cx: 0000000000000000 sp: 00007ffc637ec010 ip: 0000555b46434ac5 efl: 0000000000010246 cgf: 002b000000000033 erf: 0000000000000004 trp: 000000000000000e msk: 0000000000000000 cr2: 0000000000000008 [end of stack trace] Calling _exit(1). Core file will not be generated. Crashed report ID: No How much crashed? Whole browser Is it a problem with a plugin? No Did this work before? N/A Chrome version: 64.0.3282.186 Channel: n/a OS Version: Gentoo stable Flash Version: May or may not be related to Google Cloud print, I have both cloud and cups printers.
,
Mar 12 2018
The issue is no longer reproducable in 65.0.3325.146.
,
Mar 12 2018
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
,
Mar 13 2018
As per Comment #2, Closing this issue |
|||
►
Sign in to add a comment |
|||
Comment 1 by jmukthavaram@chromium.org
, Mar 12 2018Labels: Needs-Milestone Needs-Feedback