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

I suspect that the memory access issue is not in the lzo library, but in the pointers that have been handed to the lzo. #34

Closed
NiKola-UE opened this issue May 19, 2024 · 1 comment
Closed

I suspect that the memory access issue is not in the lzo library, but in the pointers that have been handed to the lzo. #34

NiKola-UE opened this issue May 19, 2024 · 1 comment

Comments

@NiKola-UE
Copy link 

          I suspect that the memory access issue is not in the lzo library, but in the pointers that have been handed to the lzo.
  • Are you able to collect the verbose output from the edge at the time of a crash?
  • Is there anything in particular that you are doing at the time?
  • Can you paste your (sanitised) config file?

Originally posted by @hamishcoleman in #33 (comment)
@NiKola-UE
Copy link
Author

No, I did not use N2N because there is no application for Windows. Apparently the problem is something else, but I'll open a separate issue for that when I consider what it is.

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
2 participants
@hamishcoleman @NiKola-UE