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

valgrind displays errors #292

Open
martinellison opened this issue Oct 17, 2019 · 1 comment
Open

valgrind displays errors #292

martinellison opened this issue Oct 17, 2019 · 1 comment
Labels
possibly stale This may be stale

Comments

@martinellison
Copy link

What OS are you using (uname -a, or Windows version)?

Linux xiaosan 5.2.18-200.fc30.x86_64 #1 SMP Tue Oct 1 13:14:07 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

What programming language are you using (C/C++/Go/Rust)?

gcc (GCC) 9.2.1 20190827 (Red Hat 9.2.1-1)
rustc 1.38.0 (625451e37 2019-09-23)

What did you expect to see and what you saw instead?

Expected to see no errors when running under valgrind, found many errors.

Typical error

Thread 1:
==20991== Invalid write of size 8
==20991== at 0x90C845B: ??? (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.13.7)
==20991== by 0x1FFEFFE05F: ???
==20991== by 0x1FFEFFE03F: ???
==20991== by 0x526FCBF: ???
==20991== by 0x23E829AF: ???
==20991== by 0x517254C: ??? (in /usr/lib64/libcairo.so.2.11600.0)
==20991== by 0x5174F67: ??? (in /usr/lib64/libcairo.so.2.11600.0)
==20991== by 0x1FFEFFE82F: ???
==20991== by 0x95EC021: WTF::fastFree(void*) (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.13.7)
==20991== by 0x90C5AB8: ??? (in /usr/lib64/libjavascriptcoregtk-4.0.so.18.13.7)
==20991== by 0x486DD7F: ???
==20991== by 0x486F497: ???
==20991== Address 0x1ffeffd938 is on thread 1's stack
==20991== 512 bytes below stack pointer

@TomzBench
Copy link

i see lots of memory errors from just basic example on the README. Are these errors from the OS implementations or from the webview abstractions?

@SteffenL SteffenL added the possibly stale This may be stale label Sep 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
possibly stale This may be stale
Development

No branches or pull requests

3 participants