Andri Yngvason

@dcommander I would say that it depends on how much additional information you'd need from the compositor. You'll probably need this https://wayland.app/protocols/ext-foreign-toplevel-list-v1 and this too https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/196/diffs. Then there's focus and...

If you want to be "first to market" with a general VNC solution for Wayland, you might want to consider this: https://help.realvnc.com/hc/en-us/articles/14110635000221 > Without providing an exact committed delivery date,...

> Just delete h264_encoder_destroy(encoder); to avoid the double free. That would cause a memory leak when it succeeds. The problem is that `h264_encoder_destroy` should be idempotent (do nothing with NULL),...

In case, you're not aware of this, there is an even lower log level named "trace". Feel free to open a PR for improved logging.

I fixed the null-dereference bug. It was introduced 3 week ago in 60f86fd04c500c6dd32e39a7e166d286dae68cb9

As the null-dereference bug has been fixed, I think this can be closed. Feel free to open a PR for improved logging.

This looks like it might be the result of unhandled oom. Have you checked if wayvnc leaks resources? It might not be enough to just run in `valgrind` or asan....

According to the heaptrack file, wayvnc does not leak memory. Come to think of it, oomkiller probably would have kicked in if that were the case. The quickest way to...

Sadly, that stack trace is useless to me without line numbers. Please follow the instructions to get a useful strack trace.

Follow the build instructions in README.md. Instead of `meson build`, say `meson setup build --buildtype=debug`.