Cannot reproduce. Are you able to give us the Crash id from chrome://crashes ?

Hello, 

I'm not very experienced in terms of debugging.

I'm using chromium, not chrome and so (if I'm correct) I can not report the crashes (or I didn't find the way to enable it).

Using the command line 
gdb -tui -ex=r chromium
I was able to get a backtrace of the browser (you will find a file of the gdb attached).
I'm getting a SIGSEV. MAyby that is caused by the unicode string conversion so similar.

I'll try to provide additional information if needed. 

Deleted: chromium-crash.txt 947 bytes

chromium-crash.txt 947 bytes View Download

Thank you for providing more feedback. Adding requester "dtapuska@chromium.org" to the cc list and removing "Needs-Feedback" label.

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

Unable to reproduce the issue on Ubuntu 14.04 using chrome stable #62.0.3202.75 and latest dev #64.0.3253.3
Attached a screen cast for reference.

Following are the steps followed to reproduce the issue.
------------
1. Navigated  to the site: https://www.mikrocontroller.net/topic/417908?goto=new#5194016
2. Marked the cyrillic font in the last line of the text.
3. right clicked on it.
4. Did not observe any crash or browser getting shut down.

Reporter@ - Could you please check the screen cast and please let us know if anything missed from our side. Also please check the issue on latest dev #64.0.3253.3 by creating a new profile without any apps and extensions and please let us know if the issue still persist or not.

Thanks...!!

Deleted: 780460.ogv 17.8 MB

780460.ogv 17.8 MB Download

Hello,

to your screencast: strangely, the link doesn't take you to the right posting, so I copied the relevant text:

"Aber Hauptsache, man kann pauschal auf „typisch FOSS“ meckern.  Etwas
Substanzielles beitragen – ничего, nada, wozu auch?"

If you mark the "ничего" the browser shuts down (even here in this bug report, so you can try here).

Nevertheless I created a virtual machine image for easier reproduction, but I think 1GB is too large to attach, so here is an installation guide.

# minimal system requirements: x86_64, 0.5GB RAM, 4GB Diskspace
# boot up an arch iso inside virtualbox
loadkeys de # load your keyboard map
fdisk /dev/sda
    n
    p    (enter) (enter) (enter)
    w
mkfs.ext4 /dev/sda1
mount /dev/sda1 /mnt
pacstrap /mnt base xorg-server xorg-xinit chromium virtualbox-guest-utils virtualbox-guest-modules-arch grub xorg-twm xorg-xclock xterm
arch-chroot
grub-install /dev/sda
grub-mkconfig -o /boot/grub/grub.cfg
systemctl enable vboxservice
systemctl enable dhcpcd
useradd -m -g users tester
passwd tester # I set it to "123456"
exit
reboot
# login with tester and the passwort
startx
chromium
# use "Steps to reproduce" and get a crash

I can provide the virtual machine via Dropbox later, if needed. Just tell me.

I hope that helps you
Greetings from Germany 

Thank you for providing more feedback. Adding requester "krajshree@chromium.org" to the cc list and removing "Needs-Feedback" label.

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

Reporter@ - Could you please provide the crash id from chrome://crashes.

Thanks...!!

Hello,

as a mentioned already I am using Chromium.
If I go to "chrome://crashes" a message appears:
"Crash reporting is disabled.

Crash reporting is not available in Chromium."

Thank you for providing more feedback. Adding requester "krajshree@chromium.org" to the cc list and removing "Needs-Feedback" label.

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

julian.frimmel@ Thanks for the feedback.

Tried this issue on Ubuntu 14.04 using Chromium build 61.0.3163.100 and unable to reproduce the issue.

On selecting the word 'ничего' and right clicking on it, no crash is observed.

Unable to test the issue as per comment #8, as the system requirement mentioned are not available at TE end.
Hence adding 'TE-NeedsTriageHelp' label for further updates from Dev.

Thanks...

The NextAction date has arrived: 2017-11-15

Archiving old bugs that haven't been actively assigned in over 180 days.

If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks!