Skip to content

why'd you (& xerub) alloc so much memory? #1

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
Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

why'd you (& xerub) alloc so much memory? #1

wants to merge 1 commit into from

Conversation

jakeajames
Copy link

Am I missing something?

@sbingner
Copy link
Collaborator

I haven’t looked at the kernel code for it but presumably it allocates that in blocks of that size. It’s 64k blocks that way.

haylyalhrby
haylyalhrby approved these changes Aug 11, 2020
View reviewed changes
inject.m

size_t length = (sizeof(mem) + hashesToInject * TRUST_CDHASH_LEN + 0xFFFF) & ~0xFFFF;
size_t length = (sizeof(mem) + hashesToInject * TRUST_CDHASH_LEN);
char *buffer = malloc(hashesToInject * TRUST_CDHASH_LEN);
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

https://www.snapchat.com/add

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
3 more reviewers

@chambaw chambaw chambaw approved these changes

@haylyalhrby haylyalhrby haylyalhrby approved these changes

@sa-69 sa-69 sa-69 approved these changes

Reviewers whose approvals may not affect merge requirements
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
5 participants
@jakeajames @sbingner @chambaw @haylyalhrby @sa-69