Channel to report v8 bugs?

Jiang Jiang

unread,

Apr 30, 2013, 10:09:59 AM4/30/13

to chromi...@chromium.org

Hi,

I'm trying to report a v8 bug that I can reproduce by visiting a page in current (28.0.1495.0 (Developer Build 197340)) Chromium debug ia32 build on Mac (haven't tried other platforms but it doesn't happen on Release build).

Since I can only reproduce it by visiting a page with Chromium I decided it's probably better to report it in chromium issue tracker, I entered the report twice, the bug I submitted first showed up but then got deleted immediately (in 30 seconds I think), they were Issue 236814 and Issue 236816, I don't know who/what deleted them.

I'm not familiar with Chromium bug reporting but I believe the report I sent is valid and all the information is clear. Is there any automatic mechanism to delete bug reports from the tracker? or should I report this kind of bugs elsewhere?

- Jiang

Jakob Kummerow

unread,

Apr 30, 2013, 10:20:26 AM4/30/13

to jia...@opera.com, chromium-dev

I don't know about any auto-deletion feature of Chromium bug reports; that definitely sounds weird to me.

You can file V8 bugs at https://code.google.com/p/v8/issues/entry.

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev

Jiang Jiang

unread,

Apr 30, 2013, 10:25:16 AM4/30/13

to jkum...@chromium.org, chromium-dev

On Apr 30, 2013, at 4:20 PM, Jakob Kummerow <jkum...@chromium.org> wrote:
> I don't know about any auto-deletion feature of Chromium bug reports; that definitely sounds weird to me.
>
> You can file V8 bugs at https://code.google.com/p/v8/issues/entry.

Thanks, I did try to file V8 bug here, twice, as issue 2666 and 2667, and they both got deleted immediately.

According to my colleague "someone else was complaining about the same thing happening to them in either #chromium or #blink the other day". So this might be a common problem happened to projects hosted at Google Code, I suppose, but that's hard for us outside of Google to speculate. Can someone from Chromium or V8 project help to find out why?

- Jiang

Jason Robbins

unread,

Apr 30, 2013, 10:58:26 AM4/30/13

to jia...@opera.com, jkum...@chromium.org, Chromium-dev

It sounds like your issue is being misclassified as spam. One thing that triggers it is including the same URL multiple times.

I undeleted 2666 for you.

Thanks,
jason!

Jiang Jiang

unread,

Apr 30, 2013, 11:04:25 AM4/30/13

to jrob...@google.com, jkum...@chromium.org, Chromium-dev

On Apr 30, 2013, at 4:58 PM, Jason Robbins <jrob...@google.com> wrote:
> It sounds like your issue is being misclassified as spam. One thing that triggers it is including the same URL multiple times.
>
> I undeleted 2666 for you.

Do you know what I can do to prevent this if I need to report similar bugs again? The urls are generated by the v8 JS backtrace, there is nothing I can change if I want to submit a complete backtrace.

- Jiang

Jason Robbins

unread,

Apr 30, 2013, 11:16:54 AM4/30/13

to Jiang Jiang, codesite-eng, jkum...@chromium.org, Chromium-dev

I think it can only get better when the code site team deploys different spam detection.