#5339: [media_addon_server] crash after boot ------------------------------------------+---------------------------- Reporter: diver | Owner: nobody Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: Servers/media_addon_server | Version: R1/Development Resolution: | Keywords: Blocked By: | Blocking: Has a Patch: 0 | Platform: All ------------------------------------------+---------------------------- Comment (by ttcoder): The `debugger("oops")` issue (it is indeed ''this'' ticket that tracks it, right?) has taken a sharp turn for the worse for me.. Appeared on this laptop last week, but I could get away with a reboot.. But with today's update to hrev48168 I can't possibly play much media at all without crashing media_addon_server with the "oops" tripwire.. (or sometimes the segmentation fault in float_to_float, making me think that maybe it's the mixer that's corrupting something in the address space of the server). Before getting into more involved stuff, a question.. I once got the "low resource" warning in the syslog right before the crash, at boot time when obviously there were no resources being wasted: {{{ DAEMON 'DHCP': /dev/net/broadcom570x/0: DHCP status = No error KERN: low resource memory: normal -> critical KERN: low resource memory: critical -> normal .. KERN: 605: DEBUGGER: oops KERN: debug_server: Thread 605 entered the debugger: Debugger call: `oops' }}} So my question is.. What can trigger a `low resource memory: normal -> critical` warning, apart from genuine resource waste? An add-on going into an infinite loop doing malloc() ? An add-on going in an infinite loop reading "wild" memory outside of its own memory bounds ? Bonus question -- are there open Coverity CIDs on MediaAddonServer.cpp and friends ? -- Ticket URL: <https://dev.haiku-os.org/ticket/5339#comment:17> Haiku <https://dev.haiku-os.org> Haiku - the operating system.