After rendering about 200 pages on my platform port of WebKit, I
seem to be seeing some memory leaks involving the code in KJS,
totalling 30-70MB. I have included a subgraph of the call graph for
the leaking functions. I'm not familiar with the KJS code. Is it
possible that circular
Hi Webkit Forum,
I am getting compilation errors while compiling webcore and javascriptcore
with ARM RVCT compiler version 2.2 build 559. This is my maiden attempt to
build webkit with RVCT compiler.
Three errors are appearing while compiling many source files. I have
provided Attr.cpp as an
On Sep 4, 2008, at 2:05 AM, Paul Pedriana wrote:
I see that JavaScriptCore/wtf/Vector.h has this:
// FIXME: Nothing guarantees this buffer is appropriately aligned
to
hold objects of type T.
char m_inlineBuffer[m_inlineBufferSize];
We have a bug for this:
Well the proposed solution in
https://bugs.webkit.org/show_bug.cgi?id=16925 doesn't work, as VC++
doesn't accept that syntax. And the solutions in
https://bugs.webkit.org/show_bug.cgi?id=19775 whereby a uint32_t or
uint64_t buffer are made don't work for larger types and use more memory
than
Hi !
It is not possible to disable or enable the
WTF_USE_LOW_BANDWIDTH_DISPLAY option via the ./configure options, is
this the way it should be, to not have an enormous amount of options?
And if so where would be the preferred place to activate it ?
/Mikael
This is a hardware issue and can vary between different versions. Some
hardware of course generates an unhandled exception on unaligned access;
some hardware generates an internally handled exception and restarts the
access with a different and more expensive pathway or with microcode;
some
That's a great list of subtle issues (I can add that atomicity
guarantees are different for non-aligned access sometimes) - it would
be fantastic if we could amend it with actual data, say SunSpider
results and/or DOM performance tests on Intel Mac and/or Windows.
If we got an improvement
WTF_USE_LOW_BANDWIDTH_DISPLAY should be defined in
JavaScriptCore/wtf/Platform.h for your platform.
I don't think any of the main ports in the WebKit repository use this
feature, which is why it probably doesn't work when enabled.
Please file a bug on https://bugs.webkit.org/ (and a patch to
You must check out the source code from Subversion:
http://webkit.org/building/checkout.html
Or git:
http://trac.webkit.org/wiki/UsingGitWithWebKit
Note that the code base contains code for all the ports, but each platform's
code is under a platform/platformname directory, so you know which
Here is the problem:
setenv BUILT_PRODUCTS_DIR
/Users/fzerangue/ws/WebKit/JavaScriptGlue/build/Release
The build process for WebKit requires that the BUILT_PRODUCTS_DIR be the same
for all of the projects. It looks like your Xcode is set up to always store
build products within the
That did the trick --
Thanks,
Frank
On Sep 4, 2008, at 1:49 PM, David Kilzer wrote:
Here is the problem:
setenv BUILT_PRODUCTS_DIR /Users/fzerangue/ws/WebKit/
JavaScriptGlue/build/Release
The build process for WebKit requires that the BUILT_PRODUCTS_DIR be
the same for all of the
A similar bug related to stylesheets was filed as Bug 7381 and again as Bug
15242.
https://bugs.webkit.org/show_bug.cgi?id=7381
https://bugs.webkit.org/show_bug.cgi?id=15242
It was fixed as part of Bug 16760 in r30438.
https://bugs.webkit.org/show_bug.cgi?id=16760
It looks to me like the problem is due to a template implementation not
being visible to the code being compiled. GCC and VC++ don't enforce
the C++ standard strictly here, and the CodeWarrior and EDG-based
compilers correctly flag this as invalid code. VC++ compiles templates
by essentially
13 matches
Mail list logo
