Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#54635 - [chromium] Crashes in settings and other webpages

Attached to Project: Arch Linux
Opened by dlh (dlh) - Thursday, 29 June 2017, 09:04 GMT
Last edited by Evangelos Foutras (foutrelis) - Friday, 30 June 2017, 14:56 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Evangelos Foutras (foutrelis)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Chromium crashes almost all the time on variety of websites


Additional info:
* 59.0.3071.(86|115|104|109)-1
* config and/or log files etc.

Received signal 11 SEGV_MAPERR 000000000038
#0 0x556b0b3f01b6 <unknown>
#1 0x556b0b3f062d <unknown>
#2 0x7f4205892940 <unknown>
#3 0x7f4205aaa8d8 _dl_relocate_object
#4 0x7f4205ab2783 dl_open_worker
#5 0x7f41fd31fc24 __GI__dl_catch_error
#6 0x7f4205ab20c9 _dl_open
#7 0x7f420567df26 <unknown>
#8 0x7f41fd31fc24 __GI__dl_catch_error
#9 0x7f420567e5f5 <unknown>
#10 0x7f420567dfb1 dlopen
#11 0x7f41ffe5b657 snd_dlopen
#12 0x7f41ffe56ce8 <unknown>
#13 0x7f41ffe5737c snd_config_update_r
#14 0x7f41ffe5e473 snd_device_name_hint
#15 0x556b09b62424 <unknown>
#16 0x556b09b564e5 <unknown>
#17 0x556b09b55da2 <unknown>
#18 0x556b09b563ae <unknown>
#19 0x556b09b5686a <unknown>
#20 0x556b0b44ef39 <unknown>
#21 0x556b0b485bb0 <unknown>
#22 0x556b0b410a40 <unknown>
#23 0x556b0b412108 <unknown>
#24 0x556b0b4124fe <unknown>
#25 0x556b0b4136d1 <unknown>
#26 0x556b0b40fd78 <unknown>
#27 0x556b0b4352fb <unknown>
#28 0x556b0b453996 <unknown>
#29 0x556b0b44ee36 <unknown>
#30 0x7f4205888297 start_thread
#31 0x7f41fd2e61ef __GI___clone
r8: 0000000000000030 r9: 0000000000000004 r10: 0000000000000000 r11: 0000000000000000
r12: 0000000000000006 r13: 00007f41dc1262e8 r14: 00003b47f9d3e300 r15: 0000000600000006
di: 00007f41dc126258 si: 0000000000000000 bp: 00007f41e426fb30 bx: 00007f41dc126578
dx: 0000000000000006 ax: 0000000000000000 cx: 00007f41dc1264aa sp: 00007f41e426fa30
ip: 00007f4205aaa8d8 efl: 0000000000010206 cgf: 002b000000000033 erf: 0000000000000004
trp: 000000000000000e msk: 0000000000000000 cr2: 0000000000000038
[end of stack trace]
Calling _exit(1). Core file will not be generated.


Similar thing is happening on google-chrome-stable from aur.


I am using intel graphics card.
This task depends upon

Closed by  Evangelos Foutras (foutrelis)
Friday, 30 June 2017, 14:56 GMT
Reason for closing:  Works for me
Additional comments about closing:  Can't reproduce; try reporting it upstream with a crash ID from Chrome.
Comment by Doug Newgard (Scimmia) - Thursday, 29 June 2017, 16:55 GMT
If it's happening in Chrome, it's not a chromium packaging bug.
Comment by Evangelos Foutras (foutrelis) - Thursday, 29 June 2017, 17:32 GMT
I agree with Doug. It is probably best to report it upstream with a crash ID from Chrome:

https://www.chromium.org/for-testers/bug-reporting-guidelines/reporting-crash-bug

Loading...