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

n42n / n3n

Peer to Peer VPN

https://n3n.dev

86 stars 9 forks source 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. #34

Closed NiKola-UE closed 5 months ago

NiKola-UE commented 6 months ago

          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 https://github.com/n42n/n3n/issues/33#issuecomment-2119098811

NiKola-UE commented 6 months ago

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.