Thanks for filing the issue.
Could you please provide us 16 digit latest crash id from chrome://crashes to triage further.
 

Thanks for your reply, This crash's detail on my work computer , I'll send it to you tomorrow!(crash uuid and dmp files)

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

I use Breakpad to convert the crash dmp file, But find out nothing goes wrong! May be you can help me, Thanks again!

Thanks for reply.
No need of crash dump file for now. 
Please give us 16 digit(As attached) latest crash id from chrome://crashes on latest chrome to triage further.

Deleted: crash report id.PNG 12.2 KB

	crash report id.PNG 12.2 KB View Download

cdd16967-799d-48e8-86ce-1b698ab1c40f

Deleted: crashes.zip 510 KB

crashes.zip 510 KB Download

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

there are not exists an ID like you mentioned

Deleted: crash.PNG 25.9 KB

	crash.PNG 25.9 KB View Download

gongbeidou@,
Please follow below steps to provide crash id from chrome://crashes.

1. Reproduce the issue until it become crashes
2. Goto Chrome://crashes
3. Click on 'Send Now' button (as attached)
4. Wait for few minutes(5 to 10 mins)  until it generates 16 digit (uploaded crash report id) crash id as in C#3.
5. Copy & paste that in this bug

Thanks..!

Deleted: click.PNG 10.8 KB

	click.PNG 10.8 KB View Download

I'm sorry for later, The 16 digit crash id is 746c1deda66310f8

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

And it crashed at 2018-09-22, crash id : af4e564d56f1cde7,
then it crashed again at 2018-09-25, crash id : d11a09102b96aa1e

Sorry for the delayed reply. 
Thanks for the info.
Could you please check the issue on latest stable-69.0.3497.100 on windows and provide crash id if issue still persists.

I'm soory for that, the things all the same, I update my chrome to version:69.0.3497.100, But it still crashed!

crash id : e3b4d6d358a9721a

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

It's there anybody? please help me fix this issue!! thanks a lot

 gongbeidou@
Sorry for the delay and trouble.Thanks for providing crash id in C#15, as per that seems it was older version reported crash id.
Could you please check the issue on windows with latest #70.0.3538.77 & provide us 16 digit crash id from chrome://crashes if still persists.

I update my chrome to version:70.0.3538.77, testing, I will replay to you after two or four days, Thanks.

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

ID：f6069db0a39e3aa1
version: 70.0.3538.77

please don't ask me to update my chrome again! please! please! please! help me

it sames have not fix it !

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

It sounds like the page you are running with has a javascript memory leak. And then after 5 days the page has leaked so much the process runs out of memory.

Have you tried debugging it with devtools? See https://developers.google.com/web/tools/chrome-devtools/memory-problems/ for an article describing what you can do for your website.

Since the site isn't exposed externally we can't really help you much here.

You are right! The program has a javascript memory leak, But I fix it by close current Tab after an hour and open a new Tab before current Tab closed, again and again. Then memory keeps in 350m. When it crash, The chrome debugging log reports like this every times.

[9612:4536:0917/104902.398:INFO:GrOp.h(225)] ../../third_party/skia/src/gpu/ops/GrOp.h(225): fatal error: "This should never wrap as it should only be called once for each GrOp subclass."

I don't think memory leak is the cause of 

 ../../third_party/skia/src/gpu/ops/GrOp.h(225): fatal error: "This should never wrap as it should only be called once for each GrOp subclass."

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Thanks all the same, I'll try to fix the javascript memory leak.

Over to the skia folks to comment