62d30d9e49
The AddOnManager was in the global namespace, clashing with application classes with the same name. The input_server has an AddOnManager of its own. When the shortcut_catcher filter was loaded by said AddOnManager, it in turn loaded libgame.so, which in turn loaded libmedia.so, where an AddOnManager was created for the global AddOnManager instance in libmedia.so. Unfortunately the wrong AddOnManager, the one from the input_server, was created. This lead to two AddOnManagers being active in the input_server which very well could be responsible for #11049 and #11280. This was a regression since the move of the AddOnManager from the media_server to libmedia.so in hrev47086. This also fits with the two tickets. I actually noticed the problem when debugging the shutdown process of the input_server, where the destruction of the wrong AddOnManager caused a deadlock with itself.
Haiku
Homepage | Mailing Lists | IRC Channels | Issue Tracker | API docs
Haiku is an open-source operating system that specifically targets personal computing. Inspired by the BeOS, Haiku is fast, simple to use, easy to learn and yet very powerful.
Goals
- Sensible defaults with minimal configuration required.
- Clean, clear, concise code.
- Unified desktop environment.
Trying Haiku
Haiku provides pre-built nightly images and release images. Haiku is compatible with a large variety of hardware, but in case you don't want to "take the plunge" and install Haiku on bare metal, you can install it on a virtual machine (VM) instead. If you've never used a VM before, you can follow one of the "Emulating Haiku" guides.
Compiling Haiku
See ReadMe.Compiling.
Contributing
Haiku is a meritocratic open source project with a large variety of tasks. Even if you can't write code, you can still help! Haiku needs designers, (technical) writers, translators, testers... Get involved and help out!
Contributing code
If you're submitting a patch to us, please make sure you're following the patch submitting guidelines.
If you're having trouble finding something in the source tree, you can use one of our OpenGrok servers:
- http://grok.bikemonkey.org/source (provided by Landon Fuller)
- http://code.metager.de/source/xref/haiku (provided by MetaGer)
Contributing documentation
The main piece of documentation that still needs work are the API docs (found
in the tree at src/docs/user). Just find an undocumented class, write
documentation for it, and submit a patch.
Contributing translations
See wiki:i18n.
Contributing software ports
See HaikuPorts.