Updates:
Status: WontFix
Comment #7 on issue 15354 by tk...@chromium.org: Review STACK_USE Coverity
defects in Webkit
http://code.google.com/p/chromium/issues/detail?id=15354
The patch for cid:1055 and cid:1011 was rejected.
So we have no actions for STACK_USE in WebKit.
--
You recei
Comment #6 on issue 15354 by tk...@chromium.org: Review STACK_USE Coverity
defects in Webkit
http://code.google.com/p/chromium/issues/detail?id=15354
We had better fix cid:1055 (32KB) and cid:1011 (16KB).
I'll handle them.
--
You received this message because you are listed in the owner
or C
Comment #5 on issue 15354 by tk...@chromium.org: Review STACK_USE Coverity
defects in Webkit
http://code.google.com/p/chromium/issues/detail?id=15354
ok, I'll change such issues to Class=Intentional.
--
You received this message because you are listed in the owner
or CC fields of this issue,
Updates:
Cc: dglaz...@chromium.org
Comment #3 on issue 15354 by hu...@chromium.org: Review STACK_USE Coverity
defects in Webkit
http://code.google.com/p/chromium/issues/detail?id=15354
If it is just 1-4KB usage of stack, not memory leak, we could probably
ignore those
instead of fili
Comment #2 on issue 15354 by tk...@chromium.org: Review STACK_USE Coverity
defects in Webkit
http://code.google.com/p/chromium/issues/detail?id=15354
I classified issues of src/webkit/ and src/third_party/WebKit.
* Coverity seems not to work well for WebKit's Vector and String. There
are m
Updates:
Status: Assigned
Owner: tk...@chromium.org
Comment #1 on issue 15354 by hu...@chromium.org: Review STACK_USE Coverity
defects in Webkit
http://code.google.com/p/chromium/issues/detail?id=15354
(No comment was entered for this change.)
--
You received this message beca
