QWaitCondition error

[Trindaz]

Just ran npm install and created a script from the first example in the readme opening google.com) and got this in my console output:

Using the chimera in lib QWaitCondition: cv destroy failure: Resource busy

Do I have to delve into QT to get to the bottom of this or is there something obvious I could fix in Chimera to resolve this?

[deanmao]

can you describe your use, or provide a stack trace? It's probably a bug, but it's hard to guess the problem from here.... try to reproduce it with gdb.

do these steps:

gdb node
run example.js
bt

The bt command gives you the backtrace if you get an error

[ricardobeat]

Same problem here. GDB output:

Reading symbols for shared libraries ++++......................................................................................................................................... done
Using the chimera in lib
Reading symbols for shared libraries warning: Could not find object file "/Users/catch23/current/node-chimera/build/Release/obj.target/chimera/src/top.o" - no debug information available for "top.cc".

warning: Could not find object file "/Users/catch23/current/node-chimera/build/Release/obj.target/chimera/src/cookiejar.o" - no debug information available for "cookiejar.cc".

warning: Could not find object file "/Users/catch23/current/node-chimera/build/Release/obj.target/chimera/src/chimera.o" - no debug information available for "chimera.cc".

warning: Could not find object file "/Users/catch23/current/node-chimera/build/Release/obj.target/chimera/src/browser.o" - no debug information available for "browser.cc".

......... done

[...]

Using the chimera in lib
Reading symbols for shared libraries + done
QWaitCondition: cv destroy failure: Resource busy

Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_INVALID_ADDRESS at address: 0x00000001186d5ffa
0x00007fff9442994e in memmove$VARIANT$sse3x ()

The js code:

chi.perform({
    url: 'http://127.0.0.1:' + port + '/test',
    locals: {},
    run: function(callback) {
      callback(null, 'success')
    },
    callback: function(err, result) {
        console.log(result)
    }
})

OSX 10.8, node v0.8, chimera@0.3.2

[deanmao]

Sorry guys, I'll see what's going on here. It looks like something specific to the Mac since this doesn't happen on linux... perhaps I may need some mac-specific code somewhere.