Opened 10 years ago

Last modified 4 years ago

#10738 closed bug

Running a large number of commands in KDL breaks KDL. — at Version 1

Reported by: kallisti5 Owned by: axeld
Priority: normal Milestone:
Component: System/Kernel Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Platform: All

Description (last modified by kallisti5)

After running a large number of commands in kdl, you begin getting "out of memory for command execution" for every command.

kdebug> bfs_journal 
usage: bfs_journal <ptr-to-volume>
DebugAllocPool::Free(0xcce38028): bad address
DebugAllocPool::Free(0xcce38008): bad address
kdebug> v
  vars          vnode         vnode_caches  vnode_usage   vnodes      
kdebug> v
  vars          vnode         vnode_caches  vnode_usage   vnodes      
kdebug> pt
no completions
kdebug> pt
no completions
kdebug> ptr
no completions
kdebug> ptr
no completions
kdebug> cpu
out of memory for command executionkdebug>
kdebug> threads
out of memory for command executionkdebug> 
kdebug> thread
out of memory for command executionkdebug> 
kdebug> exit
out of memory for command executionkdebug> 
kdebug> continue
out of memory for command executionkdebug> 
kdebug> reboot
out of memory for command executionkdebug> 
kdebug> bfs_journal 
out of memory for command executionkdebug>

Change History (1)

comment:1 by kallisti5, 10 years ago

Description: modified (diff)
Note: See TracTickets for help on using tickets.