Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

AwSnap – This link crashes Chrome

github.com

Post reply on HN
Print view View original

31–40 of 43 posts

Re: AwSnap – This link crashes Chrome

#31

Post by userbinator »

myworldplz wrote: post #23

I've created something similar but for Firefox: http://crashfirefox.com/ Have added new crash options for users with NoScript (even if you're blocking 302s - try right clicking).

Pushing browsers to their resource limits is fun... and makes me think that we should really have configurable limits to stop the browser consuming all RAM and crashing or affecting other applications' performance. A policy like "maximum 75% of available RAM" with a suitable cessation of further rendering when that limit is reached, with an error message, would be far better than forcing itself and all other apps into swapping and then crashing.

Re: AwSnap – This link crashes Chrome

#32

Post by reitanqild »

jlblatt wrote: post #14
jgunsch wrote: post #13

Earlier quoted context omitted.

It's not just a guess, I broke it and I fixed it :) Can I ask why you took the approach of making a Github repo to post this rather than filing a Chromium bug?

I did file a Chromium bug last week, #472347. I filed under security (as I was unsure) so it's not public, but it was pretty much immediately marked as 'Won't Fix'. Hence the repo ;)

Now this is interesting, especially the lack of a reply.

Re: AwSnap – This link crashes Chrome

#33

Post by omaranto »

greggman wrote: post #20

I hope this doesn't come across as negative but why post this on HN? Why not just file a bug on crbug.com? Browsers have bugs, all them. It seems kind of negative to turn it into a spectacle rather than just be kind and report the bug to the team.

It seems that the author did file a bug report and it almost immediately got marked WONTFIX:

https://news.ycombinator.com/item?id=9326370

Re: AwSnap – This link crashes Chrome

#34

Post by omaranto »

reitanqild wrote: post #32
jlblatt wrote: post #14

Earlier quoted context omitted.

I did file a Chromium bug last week, #472347. I filed under security (as I was unsure) so it's not public, but it was pretty much immediately marked as 'Won't Fix'. Hence the repo ;)

Now this is interesting, especially the lack of a reply.

I wouldn't call marking the bug as WONTFIX a "lack of reply".

Re: AwSnap – This link crashes Chrome

#35

Post by reitanqild »

omaranto wrote: post #34
reitanqild wrote: post #32

Earlier quoted context omitted.

Now this is interesting, especially the lack of a reply.

I wouldn't call marking the bug as WONTFIX a " lack of reply".

I see, I wasn't clear.

I talked about the lack of reply to the comment where this was pointed out.

Just asking why he didn't it and then leaving the conversation possibly means he either didn't wait for the answer or was bothered with it?

Re: AwSnap – This link crashes Chrome

#36

Post by jgunsch »

reitanqild wrote: post #35
omaranto wrote: post #34

Earlier quoted context omitted.

I wouldn't call marking the bug as WONTFIX a " lack of reply".

I see, I wasn't clear. I talked about the lack of reply to the comment where this was pointed out. Just asking why he didn't it and then leaving the conversation possibly means he either didn't wait for the answer or was bothered with it?

Sorry, last night HN didn't show me a "reply" button on the thread, so I thought maybe it tapped out at a depth of four? I'm not dodging :) [edit: does HN have account score thresholds at which different features get enabled?]

I don't have security-bugs access, but I explained offline to the OP that "Won't Fix" covers a lot of cases, including "already fixed" / "duplicate", not simply "your bug report is being ignored".

OP also sent me some more information about the BrowserStack setup, and it looks like both the M42 and M43 builds that OP was testing against are nearly a month old and before the fix (merged to M42 late in beta phase, M43's still in dev/canary stage).

Re: AwSnap – This link crashes Chrome

#37

Post by jlblatt »

reitanqild wrote: post #32
jlblatt wrote: post #14

Earlier quoted context omitted.

I did file a Chromium bug last week, #472347. I filed under security (as I was unsure) so it's not public, but it was pretty much immediately marked as 'Won't Fix'. Hence the repo ;)

Now this is interesting, especially the lack of a reply.

The dev reached out to me privately, I wouldn't infer anything based on the responses here.

Re: AwSnap – This link crashes Chrome

#38

Post by jlblatt »

jgunsch wrote: post #36
reitanqild wrote: post #35

Earlier quoted context omitted.

I see, I wasn't clear. I talked about the lack of reply to the comment where this was pointed out. Just asking why he didn't it and then leaving the conversation possibly means he either didn't wait for the answer or was bothered with it?

Sorry, last night HN didn't show me a "reply" button on the thread, so I thought maybe it tapped out at a depth of four? I'm not dodging :) [edit: does HN have account score thresholds at which different features get enabled?] I don't have security-bugs access, but I explained offline to the OP that "Won't Fix" covers a lot of cases, including "already fixed" / "duplicate", not simply "your bug report is being ignore…

TY, I'll update the readme.md when I get home tonight.

And you are right, it was initially marked as "Won't Fix" because it was not immediately reproducible, but further research yielded it being discovered as an "already fixed" dupe.

FYI it seems there is a minimum age (a minute or so) to a comment in order to reply. At least that was my experience last night.

Re: AwSnap – This link crashes Chrome

#40

Post by reitanqild »

jgunsch wrote: post #36
reitanqild wrote: post #35

Earlier quoted context omitted.

I see, I wasn't clear. I talked about the lack of reply to the comment where this was pointed out. Just asking why he didn't it and then leaving the conversation possibly means he either didn't wait for the answer or was bothered with it?

Sorry, last night HN didn't show me a "reply" button on the thread, so I thought maybe it tapped out at a depth of four? I'm not dodging :) [edit: does HN have account score thresholds at which different features get enabled?] I don't have security-bugs access, but I explained offline to the OP that "Won't Fix" covers a lot of cases, including "already fixed" / "duplicate", not simply "your bug report is being ignore…

>Sorry, last night HN didn't show me a "reply" button on the thread, so I thought maybe it tapped out at a depth of four?

Aha, the automatic flamewar limiter I guess. Happens to me as well. (clicking on the xx minutes ago link seems to help most of the time.)

> I don't have security-bugs access, but I explained offline to the OP that "Won't Fix" covers a lot of cases, including "already fixed" / "duplicate", not simply "your bug report is being ignored".

I don't know what I'd do if anyone reporting to me used wontfix for all those kind of cases. It doesn't exactly encourage bug reporting.

Post reply on HN