Skip to content
This repository has been archived by the owner on May 30, 2023. It is now read-only.

PhantomJS crash: Locking assertion failure #10658

Closed
martin-romano opened this issue Jul 13, 2012 · 4 comments
Closed

PhantomJS crash: Locking assertion failure #10658

martin-romano opened this issue Jul 13, 2012 · 4 comments
Labels

Comments

@martin-romano
Copy link

martin.t...@gmail.com commented:

Which version of PhantomJS are you using? 1.6, built from sources

What steps will reproduce the problem?

  1. any attempt to run phantomjs

Which operating system are you using?
CentOS 5.7

Did you use binary PhantomJS or did you compile it from source?
Built from source

Please provide any additional information below.

The executable that I compiled from source runs correctly on a different CentOS 5.7 box (the one I built it on) - I haven't discovered yet what's different between the machine that works and the one that fails.

When I run PhantomJS 1.6.0 Linux x86-64 (Dynamic build) downloaded from code.google.com on this system, it fails with this message:
./phantomjs: error while loading shared libraries: libexpat.so.1: cannot open shared object file: No such file or directory
This is why I tried building from source.

Here's the console output running the compiled-from-source version:
./phantomjs --version
Locking assertion failure. Backtrace:

0 /usr/lib64/libxcb-xlib.so.0 [0x318220090c]

1 /usr/lib64/libxcb-xlib.so.0(xcb_xlib_unlock+0x24) [0x3182200a14]

2 /usr/lib64/libX11.so.6 [0x318324a0f0]

3 /usr/lib64/libXfixes.so.3(XFixesQueryVersion+0x4f) [0x3188c03c9f]

4 /usr/lib64/qt47/libQtGui.so.4 [0x2b189edf28ce]

5 /usr/lib64/qt47/libQtGui.so.4(_ZN19QApplicationPrivate9constructEP9_XDisplaymm+0xde) [0x2b189ed7341e]

6 /usr/lib64/qt47/libQtGui.so.4(_ZN12QApplicationC1ERiPPci+0x72) [0x2b189ed743a2]

7 ./phantomjs [0x4217bf]

8 /lib64/libc.so.6(__libc_start_main+0xf4) [0x318061d994]

9 ./phantomjs(_ZN7QObject5eventEP6QEvent+0x349) [0x40d869]

phantomjs: xcb_xlib.c:82: xcb_xlib_unlock: Assertion `c->xlib.lock' failed.
PhantomJS has crashed. Please file a bug report at https://code.google.com/p/phantomjs/issues/entry and attach the crash dump file: /tmp/1aad3a49-68ac-3951-5068982b-30ddec3d.dmp
Aborted

Disclaimer:
This issue was migrated on 2013-03-15 from the project's former issue tracker on Google Code, Issue #658.
🌟   2 people had starred this issue at the time of migration.

@ariya
Copy link
Owner

ariya commented Jul 16, 2012

ariya.hi...@gmail.com commented:

Another CentOS problem, very similar to issue 660.

Again, this is very suspicious why PhantomJS binary needs to load the system /usr/lib64/qt47/libQtGui.so.4 at all (see my explanation -> issue 660).

@ariya
Copy link
Owner

ariya commented Mar 12, 2013

ariya.hi...@gmail.com commented:

Can you try it again with 1.8.2?

@ento
Copy link

ento commented Jul 17, 2013

I had the same error with phantomjs 1.3.0, built from source on CentOS 5.5. The error went away after upgrading to phantomjs 1.9.1 (also built from source).

Note: setting LIBXCB_ALLOW_SLOPPY_LOCK=1 also helped; it just makes libxcb ignore the assertion failure.

$ LIBXCB_ALLOW_SLOPPY_LOCK=1 DISPLAY=:0 phantomjs --version
Locking assertion failure.  Backtrace:
#0 /usr/lib64/libxcb-xlib.so.0 [0x2aaab256d90c]
#1 /usr/lib64/libxcb-xlib.so.0(xcb_xlib_unlock+0x24) [0x2aaab256da14]
#2 /usr/lib64/libX11.so.6 [0x2aaab03660f0]
#3 /usr/lib64/libXfixes.so.3(XFixesQueryVersion+0x4f) [0x2aaaaf643c9f]
#4 /usr/lib64/qt47/libQtGui.so.4 [0x2aaaac6a38ce]
#5 /usr/lib64/qt47/libQtGui.so.4(_ZN19QApplicationPrivate9constructEP9_XDisplaymm+0xde) [0x2aaaac62441e]
#6 /usr/lib64/qt47/libQtGui.so.4(_ZN12QApplicationC1ERiPPci+0x72) [0x2aaaac6253a2]
#7 phantomjs [0x415b44]
#8 /lib64/libc.so.6(__libc_start_main+0xf4) [0x2aaaae331994]
#9 phantomjs(_ZN8QWebPage13triggerActionENS_9WebActionEb+0x14a9) [0x4092f9]
1.3.0

@ghost ghost removed old.Priority-Medium labels Dec 19, 2017
@stale stale bot added the stale label Dec 26, 2019
@stale
Copy link

stale bot commented Dec 29, 2019

Due to our very limited maintenance capacity (see #14541 for more details), we need to prioritize our development focus on other tasks. Therefore, this issue will be automatically closed. In the future, if we see the need to attend to this issue again, then it will be reopened. Thank you for your contribution!

@stale stale bot closed this as completed Dec 29, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants