Aw Snap Chrome ran out of memory

View previous topic View next topic Go down

Aw Snap Chrome ran out of memory

Post by Cartoffelmos on Thu Mar 02, 2017 5:37 pm

Hi!
Suspect its related to settings done during installation, but no clue which. Hope someone can help fix this issue!

Whenever I have multiple tabs(10+) open, quite a few with running streams/videos in watch queue(twitch/youtube/liveleak and similar), or in some cases just a few in total, they all crash with the error "Aw Snap chrome ran out of memory". Never had this issue before installing K-Lite, and I've stressed Chrome quite severely in the past.

Running Full K-Lite Codec Pack 12.9.5
Chrome Version 56.0.2924.87 (64-bit)
Windows 7 SP1 64-bit
32GB RAM/4GB Pagefile, 6850K(Video disabled), GTX1080 8GB

Error happens with system memory usage way below maximum, and pagefile barely used. Tried reinstalling Chrome, no change. In the case of K-Lite I don't know what half the options actually do, so haven't dared fiddle much with it.

Tweak tool log:
Spoiler:
Codec Tweak Tool | Log file | Generated at 2017-03-02 18:33:24

##### System Information #####

OS: Windows 7 Ultimate (6.01.7601) (x64)
DirectX: 9.0c + 10 + 10.1 + 11
CPU name: Intel(R) Core(TM) i7-6850K CPU @ 3.60GHz
CPU speed: 3600 MHz (6t)
Memory: 4096 MB
Screen size: 2560x1440 (32bits) (144Hz)
Video card: NVIDIA GeForce GTX 1080
VendorID: 10de, DeviceID: 1b80
Video mem: 4096 MB
Video driver: nvd3dumx.dll (Version 21.21.13.7270) (8-25-2016) (NV 372.70)
Audio device: NVIDIA High Definition Audio
VendorID: 10de, DeviceID: 0083
Audio driver: nvhda64v.sys (Version 1.3.34.15) (5-10-2016)

##### K-Lite Codec Pack #####

KLCP version: 12.9.5
KLCP type: full

Speaker conf: 2.0

MPC renderer: EVR CP
MPC subs: ISR
MPC decoder: h264=1|3 hevc=1|3 vc1=0|3 mpeg2=0|3 vp9=1|3

##### Decoder Settings #####

LAV Video:
H264=1 HEVC=1 VP9=1 VC1=1 MPEG2=1 MPEG4=1 WMV3=0

LAV Audio:
MP3=1 AAC=1 Vorbis=1 AC3=1 DTS=1 LPCM=1 WMA=0

ffdshow (x64):
H264=0 VC1=0 MPEG2=0 XVID=0 DX50=0 DIV3=0 FLV1=0 RAW=0
MP3=0 AAC=0 AC3=0 DTS=0 TrueHD=0 Vorbis=0 Mace=1 RAW=0


##### DirectShow Filters (32-bit) #####

(A total of 68 filters, 0 shown, 68 hidden)

##### DirectShow Filters (64-bit) #####

(A total of 85 filters, 0 shown, 85 hidden)

##### ICM Class Manager (32-bit) #####

(A total of 3 filters, 0 shown, 3 hidden)

##### ICM Class Manager (64-bit) #####

(A total of 3 filters, 0 shown, 3 hidden)

##### Default source filters (32-bit) #####


(A total of 12 default source filters, 0 shown, 12 hidden)

##### Default source filters (64-bit) #####


(A total of 55 default source filters, 0 shown, 55 hidden)

##### ACM and VFW Codecs (32-bit) #####

Description: RivaTuner Video Codec
ID: VIDC.RTV1
File name: C:\Windows\SysWOW64\rtvcvfw32.dll

(A total of 16 codecs, 1 shown, 15 hidden)


##### ACM and VFW Codecs (64-bit) #####

Description: RivaTuner Video Codec
ID: VIDC.RTV1
File name: C:\Windows\system32\rtvcvfw64.dll

(A total of 14 codecs, 1 shown, 13 hidden)

I note the log is showing wrong values for RAM, Video mem and clock. Related?


Thanks for your time

Cartoffelmos

Posts : 2
Join date : 2017-03-02

View user profile

Back to top Go down

Re: Aw Snap Chrome ran out of memory

Post by Admin on Thu Mar 02, 2017 7:48 pm

Chrome uses its own internal decoders for video playback. The codec pack should not have any effect on it at all. It is likely a bug in Chrome itself. I did a quick google search and found some people that have same problem after updating to Chrome 56.

The memory in the log is indeed incorrect. It seems it doesn't show more than 4GB. Will fix that. But unrelated to your problem. What do you mean with the clock value?

Admin
Admin

Posts : 3555
Join date : 2011-06-17

View user profile http://codecs.forumotion.net

Back to top Go down

Re: Aw Snap Chrome ran out of memory

Post by Cartoffelmos on Thu Mar 02, 2017 8:45 pm

Admin wrote:Chrome uses its own internal decoders for video playback. The codec pack should not have any effect on it at all. It is likely a bug in Chrome itself. I did a quick google search and found some people that have same problem after updating to Chrome 56.

The memory in the log is indeed incorrect. It seems it doesn't show more than 4GB. Will fix that. But unrelated to your problem. What do you mean with the clock value?
If so I need to hang my head in shame and work on my google-fu, and apologise for blaming it on K-Lite. Thought I went through it extensively without finding similar reports.

The CPU is overclocked to 4400mhz, while the log shows 3600mhz(which is base non-turbo speed). Probably not an easy way to properly fetch clock speed with C1E/EIST(power-saving) active, and might not even be that relevant to have exact speed?

Cartoffelmos

Posts : 2
Join date : 2017-03-02

View user profile

Back to top Go down

Re: Aw Snap Chrome ran out of memory

Post by Admin on Thu Mar 02, 2017 9:03 pm

It shows the standard clock speed as that is a value that can easily be read from the Registry. It is not an important piece of information.

Admin
Admin

Posts : 3555
Join date : 2011-06-17

View user profile http://codecs.forumotion.net

Back to top Go down

View previous topic View next topic Back to top


 
Permissions in this forum:
You cannot reply to topics in this forum