molli.bender@ Thanks for the issue.

Tested this issue on Windows 10 on the reported version 68.0.3440.106 and the latest Canary 71.0.3543.0 and unable to reproduce the issue by following the below steps.

1. Launched Chrome and navigated to the given html page.
2. Opened Devtools and tried to delete the non-breaking space and added a normal space.
3. Couldn't observe any crash on the webpage.

Request you to provide the Crash ID from chrome://crashes, which will help in further triaging of the issue.

Also request you to retry the issue by updating chrome to the latest Stable 69.0.3497.81 and update the thread with the observations.

Thanks..

I just updated chrome to the latest version (69.0.3497.81) and I can still reproduce this problem. Crash id of one of the crashes: 73b34f80-5ac9-4223-ada1-a174a2fda4b7

I attached a video showing exactly what I did to get this issue to occur.

Deleted: Chrome devtools crash.mp4 2.3 MB

	Chrome devtools crash.mp4 2.3 MB View Download

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

molli.bender@: Thanks for providing Crash ID.

As per comment#3, the reporter has provided Crash ID, hence routing this issue to Inhouse for further triaging the issue and adding TE-NeedsTriageFromHYD label to it.

Thanks!

Thanks for the reply molli.bender@.

Unable to reproduce the issue on Windows 10 using chrome-69.0.3497.81 as per the screencast provided in C#3.

Could you provide us the latest 16 digit crash server id from chrome://crashes(as attached in screenshot) to proceed further triaging.

Note: Local crash id is not enough to get info from crash server.

Latest server crash is the following: ed9cee1e8b6cc993

jmukthavaram@
Watching your video I noticed that you didn't replace the " " in the code with a normal space when editing, which doesn't result in a crash. The text between the two html elements (in this case the non-breaking space) has to be replaced with a normal space first.

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

There's nothing to do with Blink editing.

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

commit 367f7e992a7a3581caabca95ce66336d21dccdf9
Author: Joel Einbinder <einbinder@chromium.org>
Date: Thu Oct 04 00:32:09 2018

DevTools: Don't crash when text nodes are edited to be whitespace

DevTools ignores whitespace-only text nodes. But if a text node
that previously had text becomes whitespace-only, no childNodeRemoved
event is fired and DevTools would get confused.

Bug:  880372 
Change-Id: I8f740a6e32d1c1a15a32443a2a702996028f64fa
Reviewed-on: https://chromium-review.googlesource.com/c/1257899
Commit-Queue: Joel Einbinder <einbinder@chromium.org>
Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#596443}
[modify] https://crrev.com/367f7e992a7a3581caabca95ce66336d21dccdf9/third_party/WebKit/LayoutTests/http/tests/devtools/elements/edit/set-outer-html-2-expected.txt
[add] https://crrev.com/367f7e992a7a3581caabca95ce66336d21dccdf9/third_party/WebKit/LayoutTests/http/tests/devtools/elements/edit/set-outer-html-whitespace-expected.txt
[add] https://crrev.com/367f7e992a7a3581caabca95ce66336d21dccdf9/third_party/WebKit/LayoutTests/http/tests/devtools/elements/edit/set-outer-html-whitespace.js
[modify] https://crrev.com/367f7e992a7a3581caabca95ce66336d21dccdf9/third_party/WebKit/LayoutTests/http/tests/devtools/elements/highlight/highlight-dom-updates-expected.txt
[modify] https://crrev.com/367f7e992a7a3581caabca95ce66336d21dccdf9/third_party/blink/renderer/core/inspector/inspector_dom_agent.cc
[modify] https://crrev.com/367f7e992a7a3581caabca95ce66336d21dccdf9/third_party/blink/renderer/core/inspector/inspector_dom_agent.h

Sorry if I am missing something very obvious, but I still see this issue happening for me. I believe this is supposed to be fixed though?

I guess nevermind, this bug was fixed in the current version 71.0.3578.80.