Evgeniy Sudyr wrote: > How can I help identify this bug, so developers can fix it :)
Run sudo pstat -d ld acpi_nalloc; then wait some time and run it again. Though this looks like it could be a bug not in the OpenBSD ACPI code, but in the interpreted AML code. Debugging this over email is probably going to be hard. But if you use sendbug, it will include the output of acpidump, which may be helpful. > > On Sat, Apr 4, 2015 at 6:49 PM, Ted Unangst <[email protected]> wrote: > > Evgeniy Sudyr wrote: > >> ACPI175742 18750K 18796K 78644K 572114 0 0 > > > > This looks rather high. I suspect a leak in the acpi code.
