[webkit-dev] Client application links to JavaScriptCore instead of std lib
Dear All, I have built Webkit (Process model) for Win32. I have developed a client application to use this webkit. My client application has a number of new/delete calls. Now when I run the client application it crashes at the location where memory is being freed. Call stack shows the crash point at free of JavaScriptCore. This free is inside fastmalloc.cpp. #if ENABLE(WTF_MALLOC_VALIDATION) if (!ptr) return; fastMallocValidate(ptr); Internal::ValidationHeader* header = Internal::fastMallocValidationHeader(ptr); memset(ptr, 0xCC, header-m_size); do_free(header); #else *do_free(ptr); - CRASH POINT* #endif Please let me know how can I stop my client application to get linked to JavaScriptCore memory functions. Awaiting reply. Many Thanks, Dipak ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
[webkit-dev] https://trac.webkit.org/auth/login/ down?
Hey, Trac itself seems up, but not the /auth/ parts. Anyone else seeing this? Cheers, -- pablo flouret motorola | webkit / browser team ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] https://trac.webkit.org/auth/login/ down?
The page itself can be loaded just fine, but blocking requests to static2.macosforge.org are timing out. If you wait for a minute or so the unstyled content will show up, including the login form, which works just fine. Peter On Fri, Oct 19, 2012 at 6:38 PM, Pablo Flouret pab...@motorola.com wrote: Hey, Trac itself seems up, but not the /auth/ parts. Anyone else seeing this? Cheers, -- pablo flouret motorola | webkit / browser team ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
[webkit-dev] Accessing bugs.webkit.org via XML-RPC
Hi there, Does anyone know what's the status of the XML-RPC interface on bugs.webkit.org? It seems to be there, but all calls result in a Application failed during request deserialization: no element found at line 1, column 0, byte -1 at /usr/lib64/perl5/XML/Parser.pm line 187 error. Any extra info or pointers on how to address this are super-welcome! Thanks in advance, miChou Mihai Balan | Quality Engineer / WebKit team | miba...@adobe.commailto:miba...@adobe.com | +4-031.413.3653 / x83653 | Adobe Systems Romania ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Accessing bugs.webkit.org via XML-RPC
Bill and I have talked about this in the past. I don't remember what the outcome was. Right now webkit-patch just uses Mechanize: http://trac.webkit.org/browser/trunk/Tools/Scripts/webkitpy/common/net/bugzilla We also might get some of this as part of the upgrade: https://bugs.webkit.org/show_bug.cgi?id=55882 If you (or someone else on your team) is interested in working on the upgrade, I suspect some of the CC'd would be happy to have the help. On Fri, Oct 19, 2012 at 10:53 AM, Mihai Balan miba...@adobe.com wrote: Hi there, Does anyone know what’s the status of the XML-RPC interface on bugs.webkit.org? It seems to be there, but all calls result in a Application failed during request deserialization: no element found at line 1, column 0, byte -1 at /usr/lib64/perl5/XML/Parser.pm line 187 error. Any extra info or pointers on how to address this are super-welcome! Thanks in advance, miChou Mihai Balan | Quality Engineer / WebKit team | miba...@adobe.com | +4-031.413.3653 / x83653 | Adobe Systems Romania ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] https://trac.webkit.org/auth/login/ down?
Fixed. -Bill On Oct 19, 2012, at 10:45 AM, Peter Beverloo pe...@chromium.org wrote: The page itself can be loaded just fine, but blocking requests to static2.macosforge.org are timing out. If you wait for a minute or so the unstyled content will show up, including the login form, which works just fine. Peter On Fri, Oct 19, 2012 at 6:38 PM, Pablo Flouret pab...@motorola.com wrote: Hey, Trac itself seems up, but not the /auth/ parts. Anyone else seeing this? Cheers, -- pablo flouret motorola | webkit / browser team ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Client application links to JavaScriptCore instead of std lib
Hi Dipak, You should try a clean build with build-webkit --system-malloc to force WebKit to use the system's allocator. Let me know if it solves your problem. Cheers, Zoltan On Fri, Oct 19, 2012 at 5:21 AM, dipak kumar mail.di...@gmail.com wrote: Dear All, I have built Webkit (Process model) for Win32. I have developed a client application to use this webkit. My client application has a number of new/delete calls. Now when I run the client application it crashes at the location where memory is being freed. Call stack shows the crash point at free of JavaScriptCore. This free is inside fastmalloc.cpp. #if ENABLE(WTF_MALLOC_VALIDATION) if (!ptr) return; fastMallocValidate(ptr); Internal::ValidationHeader* header = Internal::fastMallocValidationHeader(ptr); memset(ptr, 0xCC, header-m_size); do_free(header); #else *do_free(ptr); - CRASH POINT* #endif Please let me know how can I stop my client application to get linked to JavaScriptCore memory functions. Awaiting reply. Many Thanks, Dipak ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
[webkit-dev] Enabling support for high-dpi custom mouse cursors
One of the few places WebKit still doesn't support high-DPI images is custom 'cursor' CSS rules. I brought this up on www-style awhile back [1] and the consensus was that using image-set was the preferred mechanism. The CSS4 images draft spec now specifies that cursor can take any image [2], including an image-set. I'd like to take the first step by enabling -webkit-image-set support for 'cursor' rules on the chromium port (tracked in http://wkb.ug/99493https://bugs.webkit.org/show_bug.cgi?id=99493). I plan to add an ENABLE(CSS_CURSOR_SCALE) flag which adds a single 'float scale' to WebCore::Cursor that specifies the scale factor (in display pixels per logical pixel) of the custom image data in a Cursor object. It's conceivable that other mechanisms could also use this (for example, we could select the most appropriate image from a multi-resolution .cur file). Any concerns or suggestions? I've got a rough working version of a patch which I will get up for review next week sometime. Thanks, Rick [1] http://lists.w3.org/Archives/Public/www-style/2012Jul/0140.html [2] http://dev.w3.org/csswg/css4-images/#image-values ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Enabling support for high-dpi custom mouse cursors
Sounds great. Adam On Fri, Oct 19, 2012 at 1:53 PM, Rick Byers rby...@chromium.org wrote: One of the few places WebKit still doesn't support high-DPI images is custom 'cursor' CSS rules. I brought this up on www-style awhile back [1] and the consensus was that using image-set was the preferred mechanism. The CSS4 images draft spec now specifies that cursor can take any image [2], including an image-set. I'd like to take the first step by enabling -webkit-image-set support for 'cursor' rules on the chromium port (tracked in http://wkb.ug/99493). I plan to add an ENABLE(CSS_CURSOR_SCALE) flag which adds a single 'float scale' to WebCore::Cursor that specifies the scale factor (in display pixels per logical pixel) of the custom image data in a Cursor object. It's conceivable that other mechanisms could also use this (for example, we could select the most appropriate image from a multi-resolution .cur file). Any concerns or suggestions? I've got a rough working version of a patch which I will get up for review next week sometime. Thanks, Rick [1] http://lists.w3.org/Archives/Public/www-style/2012Jul/0140.html [2] http://dev.w3.org/csswg/css4-images/#image-values ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
