search

roadlabs / chromiumembedded

Automatically exported from code.google.com/p/chromiumembedded
0 stars 1 forks source link

Linux: 2272+: V8 allows_lazy_compilation check failed #1540

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
I've integrated CEF in one of my projects. With new build '3.2272.2029' I get 
following error when I try to load an url:

[0219/110034:ERROR:nss_util.cc(819)] After loading Root Certs, loaded==false: 
NSS error code: -8018

#
# Fatal error in ../../v8/src/runtime/runtime-compiler.cc, line 33
# CHECK(function->shared()->allows_lazy_compilation()) failed
#

==== C stack trace ===============================

 1: ??
 2: ??
 3: ??
Received signal 4 ILL_ILLOPN 7f8089fd852f
#0 0x7f8088b6f7ee <unknown>
#1 0x7f8088b6f323 <unknown>
#2 0x0038b2010e50 <unknown>
#3 0x7f8089fd852f <unknown>
#4 0x7f8089fd586c <unknown>
#5 0x7f8089e3399b <unknown>
#6 0x1c68801071bb <unknown>
  r8: 00007f8087f82900  r9: ffffb637b84838f0 r10: ffffb637b84838e0 r11: 00000038b1d6b8b0
 r12: 00007fff4cb0a0d0 r13: 00003637058e4001 r14: 00007f8090802fe4 r15: 00000038b1fa2708
  di: 00000038b1fa2060  si: 00000038b1fa37b0  bp: 0000000000000021  bx: 00007f809084be67
  dx: 0000000000000000  ax: 0000000000000000  cx: 00000038b1fa37b0  sp: 00007fff4cb09f70
  ip: 00007f8089fd852f efl: 0000000000010202 cgf: 0000000000000033 erf: 0000000000000000
 trp: 0000000000000006 msk: 0000000000000000 cr2: 0000000000000000
Found a corrupted memory buffer in MallocBlock (may be offset from user ptr): 
buffer index: 0, buffer ptr: 0x325ce59df700, size of buffer: 440

Previous (release) version '3.2171.1979' works. I've tested several urls. I was 
not able to load any of them.

Original issue reported on code.google.com by renegar...@gmail.com on 19 Feb 2015 at 10:15

GoogleCodeExporter commented 9 years ago 
Same issue is also visible with current trunk version '3.2295.2034'

Original comment by renegar...@gmail.com on 19 Feb 2015 at 11:03

GoogleCodeExporter commented 9 years ago 
What OS? Does the problem reproduce with the cefclient or cefsimple sample 
applications? Can you run a Debug build with gdb and post the symbolized stack 
trace?

Original comment by magreenb...@gmail.com on 20 Feb 2015 at 9:53

GoogleCodeExporter commented 9 years ago 
It's a Linux x86_64 system. It's possible to reproduce the issue with cefclient 
and a debug build of CEF-3.2295.2034 (current trunk)

The gdb output is not really better:
gdb 
/media/data/mirgu_temp/cef_binary_3.2295.2034_linux64/build/cefclient/Debug/cefc
lient 
GNU gdb (Gentoo 7.8 vanilla) 7.8
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://bugs.gentoo.org/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from 
/media/data/mirgu_temp/cef_binary_3.2295.2034_linux64/build/cefclient/Debug/cefc
lient...done.
(gdb) r
Starting program: 
/media/data/mirgu_temp/cef_binary_3.2295.2034_linux64/build/cefclient/Debug/cefc
lient 
warning: Could not load shared library symbols for linux-vdso.so.1.
Do you need "set solib-search-path" or "set sysroot"?
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[New Thread 0x7fffea707700 (LWP 1461)]
[New Thread 0x7fffe9f06700 (LWP 1466)]
[New Thread 0x7fffe9705700 (LWP 1467)]
[New Thread 0x7fffe8f04700 (LWP 1468)]
[New Thread 0x7fffec7a0700 (LWP 1469)]
[New Thread 0x7fffe8703700 (LWP 1470)]
[New Thread 0x7fffe86e2700 (LWP 1471)]
[New Thread 0x7fffe7ee1700 (LWP 1472)]
[New Thread 0x7fffe36df700 (LWP 1473)]
[New Thread 0x7fffe2ede700 (LWP 1474)]
[New Thread 0x7fffe26dd700 (LWP 1475)]
[New Thread 0x7fffe1edc700 (LWP 1476)]
[New Thread 0x7fffe16db700 (LWP 1477)]
[New Thread 0x7fffe0eda700 (LWP 1478)]
[New Thread 0x7fffe06d9700 (LWP 1479)]
[New Thread 0x7fffdfed8700 (LWP 1480)]
[New Thread 0x7fffdefe5700 (LWP 1482)]
[New Thread 0x7fffde7e4700 (LWP 1483)]
[New Thread 0x7fffddfe3700 (LWP 1484)]
[0223/154338:ERROR:nss_util.cc(819)] After loading Root Certs, loaded==false: 
NSS error code: -8018
[New Thread 0x7fffdc3a2700 (LWP 1485)]
[New Thread 0x7fffdb740700 (LWP 1486)]
[New Thread 0x7fffdae89700 (LWP 1489)]
[Thread 0x7fffdae89700 (LWP 1489) exited]
[New Thread 0x7fffdae89700 (LWP 1501)]

#
# Fatal error in ../../v8/src/runtime/runtime-compiler.cc, line 33
# Check failed: function->shared()->allows_lazy_compilation().
#

==== C stack trace ===============================

 1: ??
 2: ??
 3: ??
Received signal 4 ILL_ILLOPN 7fb7727b4e8f
#0 0x7fb7712d4ebe base::debug::StackTrace::StackTrace()
#1 0x7fb7712d49f3 base::debug::(anonymous namespace)::StackDumpSignalHandler()
#2 0x0038b2010e50 <unknown>
#3 0x7fb7727b4e8f v8::base::OS::Abort()
#4 0x7fb7727b057c V8_Fatal
#5 0x7fb7725f35d2 v8::internal::Runtime_CompileLazy()
#6 0x026f3cf0615b <unknown>
  r8: 00007fb76fc40940  r9: ffff909227df7490 r10: ffff909227df7480 r11: 00000038b1d6b8b0
 r12: 00007fffe54ec9b0 r13: 000010920d535001 r14: 00007fb7790d62d5 r15: 00000038b1fa2708
  di: 00000038b1fa2060  si: 00000038b1fa37b0  bp: 0000000000000021  bx: 00007fb779120bed
  dx: 0000000000000000  ax: 0000000000000000  cx: 00000038b1fa37b0  sp: 00007fffe54ec850
  ip: 00007fb7727b4e8f efl: 0000000000010202 cgf: 0000000000000033 erf: 0000000000000000
 trp: 0000000000000006 msk: 0000000000000000 cr2: 0000000000000000
[New Thread 0x7fffd9b8a700 (LWP 1505)]
[Thread 0x7fffd9b8a700 (LWP 1505) exited]
[New Thread 0x7fffd9b8a700 (LWP 1510)]

It seems the CEF engine is restarted automatically, so the stack trace is 
printed again and again.

Original comment by renegar...@gmail.com on 23 Feb 2015 at 2:49

GoogleCodeExporter commented 9 years ago 
Does the problem occur with release builds of libcef?

Original comment by magreenb...@gmail.com on 24 Feb 2015 at 10:48

GoogleCodeExporter commented 9 years ago 
Issue 1536 has been merged into this issue.

Original comment by magreenb...@gmail.com on 24 Feb 2015 at 10:48

GoogleCodeExporter commented 9 years ago 
Yes it works with the Release build.

Original comment by renegar...@gmail.com on 25 Feb 2015 at 6:34

GoogleCodeExporter commented 9 years ago 
This is likely a debug assertion in V8. It will need to be fixed in V8 if it 
hasn't already. Hopefully it will be resolved in a future Chromium update as 
3.2272 approaches the stable channel.

Original comment by magreenb...@gmail.com on 3 Mar 2015 at 6:44

GoogleCodeExporter commented 9 years ago

Original comment by magreenb...@gmail.com on 12 Mar 2015 at 4:22