Debugging : V8 error: Allocation failed - process out of memory (Chrome 46)

204 views
Skip to first unread message

Mark Boas

unread,
Nov 16, 2015, 8:59:36 AM11/16/15
to Chromium-discuss
Hi - (Hope this is the correct forum for issues such as these) we're experiencing an intermittent tab crash on Chrome 46.

In order to try and debug I'm running Chrome from the command line:

$ /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --enable-logging --v=1

2015-11-16 14:02:15.343 Google Chrome[3537:1157640] NSWindow warning: adding an unknown subview: <FullSizeContentView: 0x7ff46171cca0>. Break on NSLog to debug.

2015-11-16 14:02:15.345 Google Chrome[3537:1157640] Call stack:

(

0   AppKit                              0x00007fff8d76e807 -[NSThemeFrame addSubview:] + 107

1   AppKit                              0x00007fff8d76e54c -[NSView addSubview:positioned:relativeTo:] + 211

2   Google Chrome Framework             0x000000011279fa23 ChromeMain + 51042723

3   Google Chrome Framework             0x000000011279e87c ChromeMain + 51038204

4   Google Chrome Framework             0x000000011280c171 ChromeMain + 51486961

5   Google Chrome Framework             0x000000011275c17c ChromeMain + 50766076

6   Google Chrome Framework             0x00000001127681b2 ChromeMain + 50815282

7   Google Chrome Framework             0x0000000112876cbc ChromeMain + 51924028

8   Google Chrome Framework             0x000000010fac08f1 ChromeMain + 3991665

9   Google Chrome Framework             0x000000010fac0020 ChromeMain + 3989408

10  Google Chrome Framework             0x000000010fabee56 ChromeMain + 3984854

11  Google Chrome Framework             0x00000001128aa573 ChromeMain + 52135155

12  Google Chrome Framework             0x00000001128a99e3 ChromeMain + 52132195

13  Google Chrome Framework             0x00000001128a953d ChromeMain + 52131005

14  Google Chrome Framework             0x00000001128a75cf ChromeMain + 52122959

15  Google Chrome Framework             0x00000001128a737f ChromeMain + 52122367

16  Google Chrome Framework             0x00000001128a67c1 ChromeMain + 52119361

17  Google Chrome Framework             0x000000010f791697 ChromeMain + 652823

18  Google Chrome Framework             0x000000010f7905ba ChromeMain + 648506

19  Google Chrome Framework             0x0000000112aecb0a ChromeMain + 54504074

20  Google Chrome Framework             0x0000000112d8be97 ChromeMain + 57253399

21  Google Chrome Framework             0x0000000112aeb0bd ChromeMain + 54497341

22  Google Chrome Framework             0x0000000112aef005 ChromeMain + 54513541

23  Google Chrome Framework             0x0000000112ae8daf ChromeMain + 54488367

24  Google Chrome Framework             0x000000010fca77bc ChromeMain + 5986108

25  Google Chrome Framework             0x000000010fca6e16 ChromeMain + 5983638

26  Google Chrome Framework             0x000000010f6f20c2 ChromeMain + 66

27  Google Chrome                       0x000000010f6e9f39 main + 9

28  Google Chrome                       0x000000010f6e9f24 Google Chrome + 3876

29  ???                                 0x0000000000000003 0x0 + 3

)

Vector smash protection is enabled.


<--- Last few GCs --->


 1284721 ms: Scavenge 1394.4 (1437.2) -> 1394.4 (1437.2) MB, 0.6 / 0 ms (+ 0.1 ms in 1 steps since last GC) [allocation failure] [incremental marking delaying mark-sweep].

 1284757 ms: Mark-sweep 1394.4 (1437.2) -> 1393.9 (1437.2) MB, 36.2 / 0 ms (+ 25.0 ms in 18 steps since start of marking, biggest step 7.4 ms) [last resort gc].

 1284795 ms: Mark-sweep 1393.9 (1437.2) -> 1393.9 (1437.2) MB, 38.0 / 0 ms [last resort gc].



<--- JS stacktrace --->


==== JS stack trace =========================================


Security context: 0x2479568bb81 <String[32]: https://develop-webapp.trint.com>

    1: SerializeArray(aka SerializeArray) [native json.js:~51] [pc=0x2c8f23bbc49c] (this=0x3de048b04189 <undefined>,u=0x13a5bff1c7a1 <JS Array[12482]>,v=0x2f31477c59c1 <JS Function e (SharedFunctionInfo 0x2f31477b6569)>,w=0x2f31477c59a1 <JS Array[4]>,x=0x3de048b042e1 <String[0]: >,y=0x3de048b042e1 <String[0]: >)

    2: JSONSerialize(aka JSONSerialize) [native j...


V8 error: Allocation failed - process out of memory (CALL_AND_RETRY_LAST).  Current memory usage: 529 MB

1   0x109179861 ChromeMain

2   0x1092ed311 ChromeMain

3   0x1092f9d11 ChromeMain

4   0x10950cbbd ChromeMain

5   0x2c8f21d0839b


Any ideas on how to figure out this issue are gratefully received.


Thanks in advance.


Mark


madana gopal

unread,
Nov 16, 2015, 9:20:10 AM11/16/15
to ma...@trint.com, Chromium-discuss
Hi,

I think, problem is w.r.t some javascript function used by the URL. The problem looks continuous allocation of memory being made, after sometime, V8 returns allocation failed error. V8 returning error looks proper. We can try using V8 javascript profiler and try to see the JS function which is taking more CPU (which could be the place of more memory allocations too). With this, we can detect the JS function and the JS object which is allocated much memory. Thanks.

Regards,
Madan

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

---
You received this message because you are subscribed to the Google Groups "Chromium-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-discu...@chromium.org.

Mark Boas

unread,
Nov 16, 2015, 12:36:43 PM11/16/15
to Chromium-discuss, ma...@trint.com
That's helpful Madan - thanks!
Reply all
Reply to author
Forward
0 new messages