Steps to reproduce: Tools/Scripts/run-webkit-tests -1 --debug --no-timeout --no-retry-failures --no-sample-on-timeout --child-processes 1 --iterations 10 --batch-size 10000 --ios-simulator editing/undo/replace-text-in-node-preserving-markers-crash.html Then the test will crash. Following <https://trac.webkit.org/changeset/235149> (bug #188800) you can also reproduce this crash in WebKit2, omitting the -1 in the above command line, run: Tools/Scripts/run-webkit-tests --debug --no-timeout --no-retry-failures --no-sample-on-timeout --child-processes 1 --iterations 10 --batch-size 10000 --ios-simulator editing/undo/replace-text-in-node-preserving-markers-crash.html
Created attachment 347947 [details] [WK1] Stacktrace Stacktrace when running the test in WebKit1.
Created attachment 347959 [details] Patch
Comment on attachment 347959 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=347959&action=review > Source/WebCore/dom/DocumentMarker.h:129 > #if PLATFORM(IOS) I wonder if we really need these #ifdefs. Can we just stub things out on macOS?
Comment on attachment 347959 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=347959&action=review >> Source/WebCore/dom/DocumentMarker.h:129 >> #if PLATFORM(IOS) > > I wonder if we really need these #ifdefs. Can we just stub things out on macOS? Yes, but I resisted the temptation to do that now.
Comment on attachment 347959 [details] Patch Clearing flags on attachment: 347959 Committed r235256: <https://trac.webkit.org/changeset/235256>
All reviewed patches have been landed. Closing bug.
<rdar://problem/43663322>