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

crypto assertion error #5089

Closed
andrewrk opened this issue Mar 19, 2013 · 1 comment
Closed

crypto assertion error #5089

andrewrk opened this issue Mar 19, 2013 · 1 comment
Labels
crypto

Comments

@andrewrk
Copy link

When I upgraded from v0.8.22 to v0.10:

nodejs: ../src/node_crypto.cc:935: int node::crypto::Connection::HandleSSLError(const char*, int, node::crypto::Connection::ZeroStatus): Assertion `err == 1 || err == 5' failed.

Crashing hard. I can't reproduce it yet. I have a WebSocket-based chat room and it seems like some users tend to cause the assertion failure whereas others do not.
@bnoordhuis
Copy link
Member

Duplicate of #5004.

gibfahn added a commit to ibmruntimes/node that referenced this issue Mar 23, 2016
@gibfahn
deps: cherry-pick d7b81b5 from deps/v8 to deps/v8z
9bc4f00 
Original commit: d7b81b5

Float v8 patch, which has been committed to v8 master and
backported to 4.8 and 4.9 in google repos, onto 4.8 v8 in
deps to resolve nodejs#5089

Original title/commit from google repos for 4.8 is:
 PPC: [turbofan] Support for CPU models lacking isel.
 v8/v8@2e4da65

PR-URL: nodejs#5293
Fixes: nodejs#5089
Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
Reviewed-By: jbergstroem - Johan Bergström <bugs@bergstroem.nu>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
crypto
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@andrewrk @bnoordhuis