Most recent kernel where this bug did not occur: Distribution: Hardware Environment: Software Environment: Problem Description: The "memory leak" bug. The issue has been revealed by PMEMCV, is not seen by OAS (see bug 5422). Investigation shows that when the Return operation is performed from the inside Method scopes surrounding that Return operation (If, While, Switch, etc..) the memory allocations related to those scopes are not immediately released (though them are released later in AcpiDsDeleteWalkState()). This puts obstacles in the way of PMEMCV development. In order to identify new anomalies by means of PMEMCV (without complicating that instrumentation) the old anomalies being already identified should be eliminated before that. When the new scope opening AML operators (If, While, etc..) are processed uninterruptedly (no Return) the memory utilized during interpretation of them is released properly (immediately, just after completion of each of them). Steps to reproduce: Doesn't require.
Created attachment 6291 [details] ASL code applying Return from surrounding scopes. The attached demo program applies in different manner the Return operation from surrounding scopes. INTERNAL BUG NUMBER 166
Created attachment 6834 [details] Proposed patch The update was tested by the ASLTS test suite runs (all the test cases) on the following systems: - CYGWIN_NT-5.1 1.5.18(0.132/4/2) 2005-07-02 20:30 i686 unknown unknown Cygwin - Linux 2.6.5-7.191-smp #1 SMP Tue Jun 28 14:58:56 UTC 2005 i686 i686 i386 GNU/Linux for the following (all) modes supported by the ASLTS test suite: - 32-bit norm mode - 64-bit norm mode - 32-bit slack mode - 32-bit slack mode The tests were run (on the systems described above) before update, then the tests were run on those systems after update. Then results of two runs were compared. All is Ok (the relevant error fixed, no new errors).
Released in ACPICA version 20060210
Release slipped out to 20060217
ACPICA 20060608 shipped in Linux-2.6.17-git9, closed.