Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

assertion failed! #23

Closed
ericrange opened this issue Apr 1, 2015 · 7 comments
Closed

assertion failed! #23

ericrange opened this issue Apr 1, 2015 · 7 comments

Comments

@ericrange
Copy link

if i go to this line and delete it and rebuild it, all works fine!
aasd
@ericrange
Copy link
Author

i did nothing! i installed it in windows, started capturing network packages and after a while, this alert appears

@ericrange
Copy link
Author

as i said... if i delete assert(...) and rebuild cap, all works fine

@mscdex
Copy link
Owner

mscdex commented Apr 1, 2015

Out of curiousity what version of node/iojs are you using in this instance?

@ericrange
Copy link
Author

nodejs 0.12

@ericrange
Copy link
Author

this problem didnt occure accidentally. i tested it on many device (pc) and its always the same error.
i just used the capturing code from your readme file

@jinjor
Copy link

jinjor commented Apr 15, 2015

I faced the same problem.

  • Node 0.12.0
  • Windows 7 64bit

The variable status changes every time I run node, and keeps its first value in one time.
The values are 1321944 3279880 4918280 5508104...

@mscdex
Copy link
Owner

mscdex commented Sep 1, 2015

This should be fixed in master now. The issue boiled down to a change in API in libuv.

@mscdex mscdex closed this as completed Sep 1, 2015
@mwittig mwittig mentioned this issue Mar 14, 2019
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@mscdex @ericrange @jinjor