-
Notifications
You must be signed in to change notification settings - Fork 761
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.
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
zero-copy message cannot send same amount of transmission as copy message and ZMQbg/IO/0" received signal SIGABRT #614
Comments
Can you provide full working example? |
I will finish a least example and send to you next week. Maybe it is after Tuesday. |
zmqpub_multi_frame_zerocopy_github
zmqsub_multi_frame_zerocopy_github
when the receiver get the message from publisher, the publisher program will show the error bad address or segment fault. I use gdb to look up the broken point and find it is ZMQbg/IO/0" received signal SIGABRT. |
This looks more complicqtwd than it needs to be. E.g. the my_free function does nothing which will cause read from deallocated memory. Try constructing the message the simple way. |
I want to use this to transport large message to reduce the delay in the communication. In my actual program, it will crash when the message bigger than 100KB 25HZ. or I skip send the first message and it can send remained messageses. But the message cannot be deserialized. It is not the message I want to send. |
I will fix the code in my_free function and try again. Thank you. |
I found it have the error when I use zero-cpoy way to create big message and send it.
If the transimission is large, the zero- copy way the create have problem., while the copy work well.
I can send the 2MB size message and send 25Hz in copy message, but only can send 100KB message in the zero-cpoy way in the same frequency or I can send 2MB size meesage in low frequency.
This two work well. use alloc to take message or use copy way to create message.
This one cannot work. use zero-copy way to create message.
The text was updated successfully, but these errors were encountered: