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

[Bug]: access address was not malloc #34972

Closed
1 task done
smellthemoon opened this issue Jul 24, 2024 · 1 comment
Closed
1 task done

[Bug]: access address was not malloc #34972

smellthemoon opened this issue Jul 24, 2024 · 1 comment
Assignees
@smellthemoon
Labels
kind/bug Issues or changes related a bug triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@smellthemoon
Copy link
Contributor

Is there an existing issue for this?

  • I have searched the existing issues

Environment

- Milvus version:
- Deployment mode(standalone or cluster):
- MQ type(rocksmq, pulsar or kafka):    
- SDK version(e.g. pymilvus v2.0.0rc2):
- OS(Ubuntu or CentOS): 
- CPU/Memory: 
- GPU: 
- Others:

Current Behavior

string type data use memcpy to fill cause segv for not malloc enough memory in advance.

Expected Behavior

No response

Steps To Reproduce

No response

Milvus Log

No response

Anything else?

No response
@smellthemoon smellthemoon added kind/bug Issues or changes related a bug needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Jul 24, 2024
@smellthemoon
Copy link
Contributor Author

/assign

@smellthemoon smellthemoon mentioned this issue Jul 24, 2024
Merged
sre-ci-robot pushed a commit that referenced this issue Jul 24, 2024
@smellthemoon
fix: access address was not malloc (#34971)
7ec9d85 
issue: #34972  
fix string type data use memcpy to fill cause segv for not malloc enough
memory in advance.

Signed-off-by: lixinguo <[email protected]>
Co-authored-by: lixinguo <[email protected]>
@yanliang567 yanliang567 added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Jul 25, 2024
@yanliang567 yanliang567 removed their assignment Jul 25, 2024
sumitd2 pushed a commit to sumitd2/milvus that referenced this issue Aug 6, 2024
@smellthemoon @sumitd2
fix: access address was not malloc (milvus-io#34971)
b16f9c4 
issue: milvus-io#34972
fix string type data use memcpy to fill cause segv for not malloc enough
memory in advance.

Signed-off-by: lixinguo <[email protected]>
Co-authored-by: lixinguo <[email protected]>
Signed-off-by: Sumit Dubey <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@smellthemoon smellthemoon

Labels
kind/bug Issues or changes related a bug triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@smellthemoon @yanliang567