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.

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

*** ERROR: No virtual memory (2). #38

Closed
Nekotekina opened this issue Jun 20, 2014 · 13 comments
Closed

*** ERROR: No virtual memory (2). #38

Nekotekina opened this issue Jun 20, 2014 · 13 comments

Comments

@Nekotekina
Copy link

It often throws this error, but very little amount of code is generated. Also it throws assert in debug mode:

x86assembler.cpp: line 1935
ASMJIT_ASSERT(o0->getSize() == 1);

@kobalicek
Copy link
Member

I will check this out tonight, thanks for the report!

About the virtual memory manager I'm not sure without having some snippet that can reproduce the issue.

@kobalicek
Copy link
Member

Well, when using set instruction you should cast the register to 8-bit by using r8(), because it works on byte registers only. I think that I can remove this restriction, but I kept it to be strict in this case so the user knows that the rest of the register will not be cleared.

@Nekotekina
Copy link
Author

Thanks, I'll try r8(), maybe it'll fix first error too.

@kobalicek
Copy link
Member

Hi, what about the virtual memory issue, do you have more info about it?

@Nekotekina
Copy link
Author

Hi, unfortunately, I can't reproduce it, it appeared only once or twice...

@Nekotekina
Copy link
Author

Error
VirtualAllocEx() failed with error 0x57: (Wrong parameters ???)
(mSize=0x0, protect=0x40, hProcess=0xffffffffffffffff)

I added some code to detect "No virtual memory" error...
Seems size is zero for some reason.

@kobalicek
Copy link
Member

I'm confused with this one, I double-checked for possible bugs related to this, but couldn't find anything. I'm gonna merge v1.2 branch soon and add more tracking.

@Nekotekina
Copy link
Author

I changed previous message a bit, now I have full data.

@kobalicek
Copy link
Member

Okay, the only explanation would be that there is a race condition when initializing VMemLocal. If you call VMemUtil::getPageSize() at the start of your app it can workaround this one.

I think this should be fixed by #42 I'm planning to merge today or tomorrow.

@Nekotekina
Copy link
Author

Thank you, I hope it's been fixed.

@kobalicek
Copy link
Member

Hi Ivan, do you still have problems with this ? I would close otherwise.

@Nekotekina
Copy link
Author

Hi, it never occured last time. I think it can be closed.

@kobalicek
Copy link
Member

thanks, closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants