date:20160105

[webkit-dev] Clipboard API and events

2016-01-05 Thread Claudio Saavedra

Hi,

It seems to me that this API is missing from WK. Is there a reason for
this other than "nobody has stepped up yet"?

Claudio
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev

Re: [webkit-dev] Clipboard API and events

2016-01-05 Thread Michael Catanzaro

On Tue, 2016-01-05 at 16:48 +0200, Claudio Saavedra wrote:
> Hi,
> 
> It seems to me that this API is missing from WK. Is there a reason
> for
> this other than "nobody has stepped up yet"?
> 
> Claudio

What is the security model regarding the clipboard API? I'm not
enthusiastic about web pages being able to go through my clipboard
without my noticing, for example
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev

Re: [webkit-dev] Memory leak tracking in WebKit

2016-01-05 Thread Vienneau, Christopher

Hi,

I’ve resumed the memory leak tracking I was doing last year, I have some more 
details to share, hopefully you’ll be able to suggest how I might fix it.  The 
source of the leak appears to come from the below callstack.  A cache of 
animation points is being created in SVGAnimatedProperty(SVGElement* 
contextElement, const QualifiedName& attributeName, AnimatedPropertyType 
animatedPropertyType), however the destructor for SVGAnimatedProperty is never 
called.  The passed in contextElement gains a ref when the SVGAnimatedProperty 
is created, however I’m not seeing a code path where the animation points 
should be destroyed.  This effects both svg polyline and polygon, and results 
in leaking the whole page.

Thanks for any help you can provide,

Chris Vienneau


\WebCore\svg\properties\SVGAnimatedProperty.cpp
SVGAnimatedProperty::SVGAnimatedProperty(SVGElement* contextElement, const 
QualifiedName& attributeName, AnimatedPropertyType animatedPropertyType)
: m_contextElement(contextElement)
, m_attributeName(attributeName)
, m_animatedPropertyType(animatedPropertyType)
, m_isAnimating(false)
, m_isReadOnly(false)
{
}

> 
> EAWebKitd.dll!WebCore::SVGAnimatedProperty::SVGAnimatedProperty(WebCore::SVGElement
>  * contextElement, const WebCore::QualifiedName & attributeName, 
> WebCore::AnimatedPropertyType animatedPropertyType) Line 29C++

EAWebKitd.dll!WebCore::SVGAnimatedListPropertyTearOff::SVGAnimatedListPropertyTearOff(WebCore::SVGElement
 * contextElement, const WebCore::QualifiedName & attributeName, 
WebCore::AnimatedPropertyType animatedPropertyType, WebCore::SVGPointList & 
values) Line 166 C++

EAWebKitd.dll!WebCore::SVGAnimatedListPropertyTearOff::create(WebCore::SVGElement
 * contextElement, const WebCore::QualifiedName & attributeName, 
WebCore::AnimatedPropertyType animatedPropertyType, WebCore::SVGPointList & 
values) Line 159 C++

EAWebKitd.dll!WebCore::SVGAnimatedProperty::lookupOrCreateWrapper(WebCore::SVGPolyElement
 * element, const WebCore::SVGPropertyInfo * info, WebCore::SVGPointList & 
property) Line 57 C++
   
EAWebKitd.dll!WebCore::SVGPolyElement::lookupOrCreatePointsWrapper(WebCore::SVGElement
 * contextElement) Line 117C++
   EAWebKitd.dll!WebCore::SVGPolyElement::animatedPoints() Line 130 
 C++
   
EAWebKitd.dll!WebCore::updatePathFromPolylineElement(WebCore::SVGElement * 
element, WebCore::Path & path) Line 106   C++
   
EAWebKitd.dll!WebCore::updatePathFromGraphicsElement(WebCore::SVGElement * 
element, WebCore::Path & path) Line 172   C++
   EAWebKitd.dll!WebCore::RenderSVGShape::updateShapeFromElement() 
Line 84   C++
   EAWebKitd.dll!WebCore::RenderSVGPath::updateShapeFromElement() 
Line 48  C++
   EAWebKitd.dll!WebCore::RenderSVGShape::layout() Line 164   C++
   
EAWebKitd.dll!WebCore::SVGRenderSupport::layoutChildren(WebCore::RenderElement 
& start, bool selfNeedsLayout) Line 281   C++
   EAWebKitd.dll!WebCore::RenderSVGRoot::layout() Line 181  C++
   EAWebKitd.dll!WebCore::RenderElement::layoutIfNeeded() Line 135  
  C++
   EAWebKitd.dll!WebCore::RenderBlockFlow::layoutLineBoxes(bool 
relayoutChildren, WebCore::LayoutUnit & repaintLogicalTop, WebCore::LayoutUnit 
& repaintLogicalBottom) Line 1621   C++
   
EAWebKitd.dll!WebCore::RenderBlockFlow::layoutInlineChildren(bool 
relayoutChildren, WebCore::LayoutUnit & repaintLogicalTop, WebCore::LayoutUnit 
& repaintLogicalBottom) Line 652C++
   EAWebKitd.dll!WebCore::RenderBlockFlow::layoutBlock(bool 
relayoutChildren, WebCore::LayoutUnit pageLogicalHeight) Line 484C++
   EAWebKitd.dll!WebCore::RenderBlock::layout() Line 930
  C++
   
EAWebKitd.dll!WebCore::RenderBlockFlow::layoutBlockChild(WebCore::RenderBox & 
child, WebCore::RenderBlockFlow::MarginInfo & marginInfo, WebCore::LayoutUnit & 
previousFloatLogicalBottom, WebCore::LayoutUnit & maxFloatLogicalBottom) Line 
712C++
   EAWebKitd.dll!WebCore::RenderBlockFlow::layoutBlockChildren(bool 
relayoutChildren, WebCore::LayoutUnit & maxFloatLogicalBottom) Line 633 
   C++
   EAWebKitd.dll!WebCore::RenderBlockFlow::layoutBlock(bool 
relayoutChildren, WebCore::LayoutUnit pageLogicalHeight) Line 488C++
   EAWebKitd.dll!WebCore::RenderBlock::layout() Line 930
  C++
   
EAWebKitd.dll!WebCore::RenderBlockFlow::layoutBlockChild(WebCore::RenderBox & 
child, WebCore::RenderBlockFlow::MarginInfo & marginInfo, WebCore::LayoutUnit & 
previousFloatLogicalBottom, WebCore::LayoutUnit & maxFloatLogicalBottom) Line 
712

Re: [webkit-dev] Memory leak tracking in WebKit

2016-01-05 Thread Simon Fraser

This sounds like a bug that would affect all WebKit ports. Can you file a 
bugs.webkit.org bug, and continue investigation there?

Simon

> On Jan 5, 2016, at 12:03 PM, Vienneau, Christopher  wrote:
> 
> Hi,
>  
> I’ve resumed the memory leak tracking I was doing last year, I have some more 
> details to share, hopefully you’ll be able to suggest how I might fix it.  
> The source of the leak appears to come from the below callstack.  A cache of 
> animation points is being created in SVGAnimatedProperty(SVGElement* 
> contextElement, const QualifiedName& attributeName, AnimatedPropertyType 
> animatedPropertyType), however the destructor for SVGAnimatedProperty is 
> never called.  The passed in contextElement gains a ref when the 
> SVGAnimatedProperty is created, however I’m not seeing a code path where the 
> animation points should be destroyed.  This effects both svg polyline and 
> polygon, and results in leaking the whole page.
>  
> Thanks for any help you can provide,
>  
> Chris Vienneau
>  
>  
> \WebCore\svg\properties\SVGAnimatedProperty.cpp
> SVGAnimatedProperty::SVGAnimatedProperty(SVGElement* contextElement, const 
> QualifiedName& attributeName, AnimatedPropertyType animatedPropertyType)
> : m_contextElement(contextElement)
> , m_attributeName(attributeName)
> , m_animatedPropertyType(animatedPropertyType)
> , m_isAnimating(false)
> , m_isReadOnly(false)
> {
> }
>  
> > 
> > EAWebKitd.dll!WebCore::SVGAnimatedProperty::SVGAnimatedProperty(WebCore::SVGElement
> >  * contextElement, const WebCore::QualifiedName & attributeName, 
> > WebCore::AnimatedPropertyType animatedPropertyType) Line 29
> > C++
> 
> EAWebKitd.dll!WebCore::SVGAnimatedListPropertyTearOff::SVGAnimatedListPropertyTearOff(WebCore::SVGElement
>  * contextElement, const WebCore::QualifiedName & attributeName, 
> WebCore::AnimatedPropertyType animatedPropertyType, WebCore::SVGPointList & 
> values) Line 166 C++
> 
> EAWebKitd.dll!WebCore::SVGAnimatedListPropertyTearOff::create(WebCore::SVGElement
>  * contextElement, const WebCore::QualifiedName & attributeName, 
> WebCore::AnimatedPropertyType animatedPropertyType, WebCore::SVGPointList & 
> values) Line 159 C++
> 
> EAWebKitd.dll!WebCore::SVGAnimatedProperty::lookupOrCreateWrapper(WebCore::SVGPolyElement
>  * element, const WebCore::SVGPropertyInfo * info, WebCore::SVGPointList & 
> property) Line 57 C++
>
> EAWebKitd.dll!WebCore::SVGPolyElement::lookupOrCreatePointsWrapper(WebCore::SVGElement
>  * contextElement) Line 117C++
>EAWebKitd.dll!WebCore::SVGPolyElement::animatedPoints() Line 
> 130  C++
>
> EAWebKitd.dll!WebCore::updatePathFromPolylineElement(WebCore::SVGElement * 
> element, WebCore::Path & path) Line 106   C++
>
> EAWebKitd.dll!WebCore::updatePathFromGraphicsElement(WebCore::SVGElement * 
> element, WebCore::Path & path) Line 172   C++
>
> EAWebKitd.dll!WebCore::RenderSVGShape::updateShapeFromElement() Line 84   
> C++
>EAWebKitd.dll!WebCore::RenderSVGPath::updateShapeFromElement() 
> Line 48  C++
>EAWebKitd.dll!WebCore::RenderSVGShape::layout() Line 164   C++
>
> EAWebKitd.dll!WebCore::SVGRenderSupport::layoutChildren(WebCore::RenderElement
>  & start, bool selfNeedsLayout) Line 281   C++
>EAWebKitd.dll!WebCore::RenderSVGRoot::layout() Line 181  
> C++
>EAWebKitd.dll!WebCore::RenderElement::layoutIfNeeded() Line 
> 135C++
>EAWebKitd.dll!WebCore::RenderBlockFlow::layoutLineBoxes(bool 
> relayoutChildren, WebCore::LayoutUnit & repaintLogicalTop, 
> WebCore::LayoutUnit & repaintLogicalBottom) Line 1621   C++
>
> EAWebKitd.dll!WebCore::RenderBlockFlow::layoutInlineChildren(bool 
> relayoutChildren, WebCore::LayoutUnit & repaintLogicalTop, 
> WebCore::LayoutUnit & repaintLogicalBottom) Line 652C++
>EAWebKitd.dll!WebCore::RenderBlockFlow::layoutBlock(bool 
> relayoutChildren, WebCore::LayoutUnit pageLogicalHeight) Line 484C++
>EAWebKitd.dll!WebCore::RenderBlock::layout() Line 930  
> C++
>
> EAWebKitd.dll!WebCore::RenderBlockFlow::layoutBlockChild(WebCore::RenderBox & 
> child, WebCore::RenderBlockFlow::MarginInfo & marginInfo, WebCore::LayoutUnit 
> & previousFloatLogicalBottom, WebCore::LayoutUnit & maxFloatLogicalBottom) 
> Line 712C++
>
> EAWebKitd.dll!WebCore::RenderBlockFlow::layoutBlockChildren(bool 
> relayoutChildren, WebCore::LayoutUnit & maxFloatLogicalBottom) Line 633   
>  C++
>EAWebKitd.dll!WebCore::RenderBlockFlow::layoutBlock(bool 
>

Re: [webkit-dev] Memory leak tracking in WebKit

2016-01-05 Thread Vienneau, Christopher

Thanks for suggesting that Simon, I’ve now opened the bug:
https://bugs.webkit.org/show_bug.cgi?id=152759

Chris

From: simon.fra...@apple.com [mailto:simon.fra...@apple.com]
Sent: Tuesday, January 05, 2016 12:09 PM
To: Vienneau, Christopher 
Cc: WebKit Development 
Subject: Re: [webkit-dev] Memory leak tracking in WebKit

This sounds like a bug that would affect all WebKit ports. Can you file a 
bugs.webkit.org bug, and continue investigation there?

Simon

On Jan 5, 2016, at 12:03 PM, Vienneau, Christopher 
> wrote:

Hi,

I’ve resumed the memory leak tracking I was doing last year, I have some more 
details to share, hopefully you’ll be able to suggest how I might fix it.  The 
source of the leak appears to come from the below callstack.  A cache of 
animation points is being created in SVGAnimatedProperty(SVGElement* 
contextElement, const QualifiedName& attributeName, AnimatedPropertyType 
animatedPropertyType), however the destructor for SVGAnimatedProperty is never 
called.  The passed in contextElement gains a ref when the SVGAnimatedProperty 
is created, however I’m not seeing a code path where the animation points 
should be destroyed.  This effects both svg polyline and polygon, and results 
in leaking the whole page.

Thanks for any help you can provide,

Chris Vienneau


\WebCore\svg\properties\SVGAnimatedProperty.cpp
SVGAnimatedProperty::SVGAnimatedProperty(SVGElement* contextElement, const 
QualifiedName& attributeName, AnimatedPropertyType animatedPropertyType)
: m_contextElement(contextElement)
, m_attributeName(attributeName)
, m_animatedPropertyType(animatedPropertyType)
, m_isAnimating(false)
, m_isReadOnly(false)
{
}

> 
> EAWebKitd.dll!WebCore::SVGAnimatedProperty::SVGAnimatedProperty(WebCore::SVGElement
>  * contextElement, const WebCore::QualifiedName & attributeName, 
> WebCore::AnimatedPropertyType animatedPropertyType) Line 29C++

EAWebKitd.dll!WebCore::SVGAnimatedListPropertyTearOff::SVGAnimatedListPropertyTearOff(WebCore::SVGElement
 * contextElement, const WebCore::QualifiedName & attributeName, 
WebCore::AnimatedPropertyType animatedPropertyType, WebCore::SVGPointList & 
values) Line 166 C++

EAWebKitd.dll!WebCore::SVGAnimatedListPropertyTearOff::create(WebCore::SVGElement
 * contextElement, const WebCore::QualifiedName & attributeName, 
WebCore::AnimatedPropertyType animatedPropertyType, WebCore::SVGPointList & 
values) Line 159 C++

EAWebKitd.dll!WebCore::SVGAnimatedProperty::lookupOrCreateWrapper(WebCore::SVGPolyElement
 * element, const WebCore::SVGPropertyInfo * info, WebCore::SVGPointList & 
property) Line 57 C++
   
EAWebKitd.dll!WebCore::SVGPolyElement::lookupOrCreatePointsWrapper(WebCore::SVGElement
 * contextElement) Line 117C++
   EAWebKitd.dll!WebCore::SVGPolyElement::animatedPoints() Line 130 
 C++
   
EAWebKitd.dll!WebCore::updatePathFromPolylineElement(WebCore::SVGElement * 
element, WebCore::Path & path) Line 106   C++
   
EAWebKitd.dll!WebCore::updatePathFromGraphicsElement(WebCore::SVGElement * 
element, WebCore::Path & path) Line 172   C++
   EAWebKitd.dll!WebCore::RenderSVGShape::updateShapeFromElement() 
Line 84   C++
   EAWebKitd.dll!WebCore::RenderSVGPath::updateShapeFromElement() 
Line 48  C++
   EAWebKitd.dll!WebCore::RenderSVGShape::layout() Line 164   C++
   
EAWebKitd.dll!WebCore::SVGRenderSupport::layoutChildren(WebCore::RenderElement 
& start, bool selfNeedsLayout) Line 281   C++
   EAWebKitd.dll!WebCore::RenderSVGRoot::layout() Line 181  C++
   EAWebKitd.dll!WebCore::RenderElement::layoutIfNeeded() Line 135  
  C++
   EAWebKitd.dll!WebCore::RenderBlockFlow::layoutLineBoxes(bool 
relayoutChildren, WebCore::LayoutUnit & repaintLogicalTop, WebCore::LayoutUnit 
& repaintLogicalBottom) Line 1621   C++
   
EAWebKitd.dll!WebCore::RenderBlockFlow::layoutInlineChildren(bool 
relayoutChildren, WebCore::LayoutUnit & repaintLogicalTop, WebCore::LayoutUnit 
& repaintLogicalBottom) Line 652C++
   EAWebKitd.dll!WebCore::RenderBlockFlow::layoutBlock(bool 
relayoutChildren, WebCore::LayoutUnit pageLogicalHeight) Line 484C++
   EAWebKitd.dll!WebCore::RenderBlock::layout() Line 930
  C++
   
EAWebKitd.dll!WebCore::RenderBlockFlow::layoutBlockChild(WebCore::RenderBox & 
child, WebCore::RenderBlockFlow::MarginInfo & marginInfo, WebCore::LayoutUnit & 
previousFloatLogicalBottom, WebCore::LayoutUnit & maxFloatLogicalBottom) Line 
712C++

Re: [webkit-dev] Memory leak tracking in WebKit

2016-01-05 Thread Said Abou-Hallawa

This seems to be a reference cycle between SVGAnimatedListPropertyTearOff and 
SVGListPropertyTearOff. In SVGAnimatedListPropertyTearOff::animVal(), m_animVal 
is assigned to a new Ref but this new Ref increments 
the refcount of this. This looks similar to 
https://bugs.webkit.org/show_bug.cgi?id=151810.

> On Jan 5, 2016, at 2:19 PM, Vienneau, Christopher  wrote:
> 
> Thanks for suggesting that Simon, I’ve now opened the bug:
> https://bugs.webkit.org/show_bug.cgi?id=152759 
> 
>  
> Chris
>  
> From: simon.fra...@apple.com [mailto:simon.fra...@apple.com] 
> Sent: Tuesday, January 05, 2016 12:09 PM
> To: Vienneau, Christopher 
> Cc: WebKit Development 
> Subject: Re: [webkit-dev] Memory leak tracking in WebKit
>  
> This sounds like a bug that would affect all WebKit ports. Can you file a 
> bugs.webkit.org  bug, and continue investigation 
> there?
>  
> Simon
>  
> On Jan 5, 2016, at 12:03 PM, Vienneau, Christopher  > wrote:
>  
> Hi,
>  
> I’ve resumed the memory leak tracking I was doing last year, I have some more 
> details to share, hopefully you’ll be able to suggest how I might fix it.  
> The source of the leak appears to come from the below callstack.  A cache of 
> animation points is being created in SVGAnimatedProperty(SVGElement* 
> contextElement, const QualifiedName& attributeName, AnimatedPropertyType 
> animatedPropertyType), however the destructor for SVGAnimatedProperty is 
> never called.  The passed in contextElement gains a ref when the 
> SVGAnimatedProperty is created, however I’m not seeing a code path where the 
> animation points should be destroyed.  This effects both svg polyline and 
> polygon, and results in leaking the whole page.
>  
> Thanks for any help you can provide,
>  
> Chris Vienneau
>  
>  
> \WebCore\svg\properties\SVGAnimatedProperty.cpp
> SVGAnimatedProperty::SVGAnimatedProperty(SVGElement* contextElement, const 
> QualifiedName& attributeName, AnimatedPropertyType animatedPropertyType)
> : m_contextElement(contextElement)
> , m_attributeName(attributeName)
> , m_animatedPropertyType(animatedPropertyType)
> , m_isAnimating(false)
> , m_isReadOnly(false)
> {
> }
>  
> > 
> > EAWebKitd.dll!WebCore::SVGAnimatedProperty::SVGAnimatedProperty(WebCore::SVGElement
> >  * contextElement, const WebCore::QualifiedName & attributeName, 
> > WebCore::AnimatedPropertyType animatedPropertyType) Line 29
> > C++
> 
> EAWebKitd.dll!WebCore::SVGAnimatedListPropertyTearOff::SVGAnimatedListPropertyTearOff(WebCore::SVGElement
>  * contextElement, const WebCore::QualifiedName & attributeName, 
> WebCore::AnimatedPropertyType animatedPropertyType, WebCore::SVGPointList & 
> values) Line 166 C++
> 
> EAWebKitd.dll!WebCore::SVGAnimatedListPropertyTearOff::create(WebCore::SVGElement
>  * contextElement, const WebCore::QualifiedName & attributeName, 
> WebCore::AnimatedPropertyType animatedPropertyType, WebCore::SVGPointList & 
> values) Line 159 C++
> 
> EAWebKitd.dll!WebCore::SVGAnimatedProperty::lookupOrCreateWrapper(WebCore::SVGPolyElement
>  * element, const WebCore::SVGPropertyInfo * info, WebCore::SVGPointList & 
> property) Line 57 C++
>
> EAWebKitd.dll!WebCore::SVGPolyElement::lookupOrCreatePointsWrapper(WebCore::SVGElement
>  * contextElement) Line 117C++
>EAWebKitd.dll!WebCore::SVGPolyElement::animatedPoints() Line 
> 130  C++
>
> EAWebKitd.dll!WebCore::updatePathFromPolylineElement(WebCore::SVGElement * 
> element, WebCore::Path & path) Line 106   C++
>
> EAWebKitd.dll!WebCore::updatePathFromGraphicsElement(WebCore::SVGElement * 
> element, WebCore::Path & path) Line 172   C++
>
> EAWebKitd.dll!WebCore::RenderSVGShape::updateShapeFromElement() Line 84   
> C++
>EAWebKitd.dll!WebCore::RenderSVGPath::updateShapeFromElement() 
> Line 48  C++
>EAWebKitd.dll!WebCore::RenderSVGShape::layout() Line 164   C++
>
> EAWebKitd.dll!WebCore::SVGRenderSupport::layoutChildren(WebCore::RenderElement
>  & start, bool selfNeedsLayout) Line 281   C++
>EAWebKitd.dll!WebCore::RenderSVGRoot::layout() Line 181  
> C++
>EAWebKitd.dll!WebCore::RenderElement::layoutIfNeeded() Line 
> 135C++
>EAWebKitd.dll!WebCore::RenderBlockFlow::layoutLineBoxes(bool 
> relayoutChildren, WebCore::LayoutUnit & repaintLogicalTop, 
> WebCore::LayoutUnit & repaintLogicalBottom) Line 1621   C++
>
> EAWebKitd.dll!WebCore::RenderBlockFlow::layoutInlineChildren(bool 
>

Re: [webkit-dev] Fwd: cross compile webkitgtk+

2016-01-05 Thread Bryan

please help me as i am stuck with this issue.
On Jan 5, 2016 6:19 PM, "Bryan"  wrote:

> Hi,
>  I have used webkitgtk-3.0 for building my application and  i am
> getting issue while loading web page. it shows me white screen.
>
> i am trying to compile latest webkitgtk code from svn but i dont even
> found webkit.h header file.
>
> I need help to build one sample webkitgtk based c++ application. also i
> need steps to cross compile latest webkitgtk on arm.
>
> Please help me.
>
> thanks
> bryan
> -- Forwarded message --
> From: "Bryan" 
> Date: Dec 30, 2015 11:08 PM
> Subject: cross compile webkitgtk+
> To: 
> Cc:
>
> Dear All,
> Can somebody will guide to cross compile webkitgk+ for arm
> from my x86 machine.
> I need to know what all settings or path for toolchain need to be set.
> If somebody have any build script, please share with me.
>
>
> Thanks
> Bryan
>
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev

[webkit-dev] Clipboard API and events

Re: [webkit-dev] Clipboard API and events

Re: [webkit-dev] Memory leak tracking in WebKit

Re: [webkit-dev] Memory leak tracking in WebKit

Re: [webkit-dev] Memory leak tracking in WebKit

Re: [webkit-dev] Memory leak tracking in WebKit

Re: [webkit-dev] Fwd: cross compile webkitgtk+

7 matches

Site Navigation

Mail list logo

Footer information