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

Use symbolic link to avoid two appscope libraries in one process #1584

Closed
jrcheli opened this issue Jul 12, 2023 · 0 comments · Fixed by #1583
Closed

Use symbolic link to avoid two appscope libraries in one process #1584

jrcheli opened this issue Jul 12, 2023 · 0 comments · Fixed by #1583
Assignees
Labels
bug Something isn't working
Milestone

Comments

@jrcheli
Copy link
Contributor

jrcheli commented Jul 12, 2023

On upgrade of appscope, when using rules, it's possible to have /etc/ld.so.preload refer to one version of the appscope library, and LD_PRELOAD refer to another. When this happens, the loader can load both versions of the appscope library into the same process.

This only occurs when the checksums of the libraries are different, but this will be the case when moving from v1.4.0 to v1.4.1, as an example.

When one process has multiple appscope libraries loaded into it, we've observed crashes in the memory subsystem. We believe this is due to each library using it's own memory subsystem; the crash occurring when memory is allocated by one, and an attempt is made to free it by the other.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants