[ATSPI] Querying The `Name` property of an `Accessible` causes the QT Application To Segfault

When receiving an event of a new accessible being created, for example, with a path of `/org/a11y/atspi/accessible/2147483721`, when querying certain properties of the element, for example the `Name` property as defined in [at-spi2-core](https://gitlab.gnome.org/GNOME/at-spi2-core/-/blob/main/xml/Accessible.xml#L22), the QT application seems to crash.
This can be replicated with the current master branch of the [Odilia screen reader project](https://github.com/odilia-app/odilia).

I've confirmed this happens on both VLC and Virtualbox, but I can't tell exactly which version these are running since they are not dynamically linked to any QT library (as reported by `ldd`) and activating debugging doesn't mention the QT version in either application. So I've selected the latest release, even if this is not the case. If there is some way for me to find the version within those two applications, or if there is a minimal example I may be able to compile to test on the latest QT, I'd be willing to do that as well.

Strangely, the Orca screen reader appears to know how to query these elements, because it does not cause the QT application to crash at all. This could very well also be an issue/workaround in the `at-spi2-core` library which Orca relies on; whereas Odilia communicates directly over DBus.

I've attached the DBus logs for all accessibility events during the time of the crash, and I could potentially attach a stack trace of the crashed QT application, but I may need instructions on how to do so.

If I've created this issue in error, or if you believe there is a better place to report this, please feel free to send me there. Or, if I've not followed any norms that you normally use here, please let me know.

Thanks a bunch for all the work that you do! I can't imagine maintaining a project as big as QT