Branch: refs/heads/main
Home: https://github.com/WebKit/WebKit
Commit: 52383c657de22cc521391fd28d9a3fb97b283281
https://github.com/WebKit/WebKit/commit/52383c657de22cc521391fd28d9a3fb97b283281
Author: Jean-Yves Avenard <j...@apple.com>
Date: 2025-08-06 (Wed, 06 Aug 2025)
Changed paths:
M Source/WebCore/platform/SharedBuffer.cpp
M Source/WebCore/platform/SharedBuffer.h
M Source/WebCore/platform/cf/SharedBufferCF.cpp
M Source/WebCore/platform/cocoa/SharedBufferCocoa.mm
M Source/WebCore/workers/ScriptBuffer.cpp
M Tools/TestWebKitAPI/Tests/WebCore/SharedBuffer.cpp
Log Message:
-----------
FragmentedSharedBuffer should always be immutable.
https://bugs.webkit.org/show_bug.cgi?id=296798
rdar://157282731
Reviewed by Gerald Squelart.
Following this change, a FragmentedSharedBuffer is now always immutable
and can never be modified once created.
The SharedBufferBuilder is the object where DataSegmentVector is now kept
and updated.
Upon call to SharedBufferBuilder::take or get, the SharedBuffer or
FragmentedSharedBuffer
shared buffer will be lazily created.
Due to how ScriptBuffer uses a SharedBufferBuilder::get() we have to keep this
SharedBuffer alive until the next time a segment is added (or cleared).
This dangerous will be rectified in a follow-up change.
Covered by existing API tests and more added to broaden coverage.
Canonical link: https://commits.webkit.org/298282@main
To unsubscribe from these emails, change your notification settings at
https://github.com/WebKit/WebKit/settings/notifications
_______________________________________________
webkit-changes mailing list
webkit-changes@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-changes
