RESOLVED CONFIGURATION CHANGED262276
ASSERTION FAILED: availableWidth >= 0 /app/webkit/Source/WebCore/layout/formattingContexts/inline/text/TextUtil.cpp(228)
https://bugs.webkit.org/show_bug.cgi?id=262276
Summary ASSERTION FAILED: availableWidth >= 0 /app/webkit/Source/WebCore/layout/forma...
djinn
Reported 2023-09-27 23:02:22 PDT
Created attachment 467949 [details] testcase to trigger the crash ASSERTION FAILED: availableWidth >= 0 /app/webkit/Source/WebCore/layout/formattingContexts/inline/text/TextUtil.cpp(228) : static WebCore::Layout::TextUtil::WordBreakLeft WebCore::Layout::TextUtil::breakWord(const WebCore::Layout::InlineTextBox&, size_t, size_t, WebCore::Layout::InlineLayoutUnit, WebCore::Layout::InlineLayoutUnit, WebCore::Layout::InlineLayoutUnit, const WebCore::FontCascade&) The minimized testcase will be uploaded as soon as possible.
Attachments
testcase to trigger the crash (2.24 MB, text/html)
2023-09-27 23:02 PDT, djinn
no flags
minimized testcase (23.78 KB, text/html)
2024-03-12 07:40 PDT, djinn
no flags
Radar WebKit Bug Importer
Comment 1 2023-10-04 23:03:19 PDT
djinn
Comment 2 2023-11-03 23:04:30 PDT
Hello, I would like to ask if a previously submitted bug is still not processed or unconfirmed, was it submitted in the wrong way? Or is it something else? Should I offer more info?
alan
Comment 3 2023-11-04 10:48:27 PDT
(In reply to djinn from comment #2) > Hello, I would like to ask if a previously submitted bug is still not > processed or unconfirmed, was it submitted in the wrong way? Or is it > something else? Should I offer more info? I think these bug reports are great, I was just waiting for the minimized test cases. It's a rather cumbersome task to reduce such verbose fuzzer reports manually.
djinn
Comment 4 2024-03-12 07:40:32 PDT
Created attachment 470315 [details] minimized testcase Sorry for uploading this trimmed testcase lately. Hope it cloud help to figure out the problem.
alan
Comment 5 2024-03-13 16:45:05 PDT
I am unable to reproduce this on tot webkit (276039@main)
Note You need to log in before you can comment on or make changes to this bug.