WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
35907
Allow custom memory allocation control for AtomicString class
https://bugs.webkit.org/show_bug.cgi?id=35907
Summary
Allow custom memory allocation control for AtomicString class
Zoltan Horvath
Reported
2010-03-09 01:03:09 PST
Inherits the following class from FastAllocBase because it is instantiated by 'new': class name - instantiated at: WebCore/'location' AtomicString - WebCore/html/HTMLTableElement.cpp:525
Attachments
proposed patch
(1.12 KB, patch)
2010-03-09 01:04 PST
,
Zoltan Horvath
no flags
Details
Formatted Diff
Diff
View All
Add attachment
proposed patch, testcase, etc.
Zoltan Horvath
Comment 1
2010-03-09 01:04:47 PST
Created
attachment 50281
[details]
proposed patch
Eric Seidel (no email)
Comment 2
2010-03-15 15:34:23 PDT
Comment on
attachment 50281
[details]
proposed patch There was concern expressed before that these were making classes bigger? Was that issue ever resolved? Otherwise this change looks fine.
Eric Seidel (no email)
Comment 3
2010-03-15 15:58:03 PDT
Attachment 50281
[details]
was posted by a committer and has review+, assigning to Zoltan Horvath for commit.
Zoltan Horvath
Comment 4
2010-03-17 00:40:11 PDT
Comment on
attachment 50281
[details]
proposed patch Clearing flags on attachment: 50281 Committed
r56100
: <
http://trac.webkit.org/changeset/56100
>
Zoltan Horvath
Comment 5
2010-03-17 00:40:19 PDT
All reviewed patches have been landed. Closing bug.
Zoltan Horvath
Comment 6
2010-03-17 00:42:06 PDT
(In reply to
comment #2
)
> There was concern expressed before that these were making classes bigger? Was > that issue ever resolved? Otherwise this change looks fine.
I opened a bug for it (
bug #33896
) and made a static analysis on the classes.
Darin Adler
Comment 7
2010-03-17 09:02:03 PDT
(In reply to
comment #6
)
> (In reply to
comment #2
) > > There was concern expressed before that these were making classes bigger? Was > > that issue ever resolved? Otherwise this change looks fine. > > I opened a bug for it (
bug #33896
) and made a static analysis on the classes.
I'm not sure what the status is, though. If additional introduction of these changes are making our classes still bigger maybe we should hold off until we decide if that's OK.
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug