# New Ticket Created by Andy Dougherty
# Please include the string: [perl #42620]
# in the subject line of all future correspondence about this issue.
# <URL: http://rt.perl.org/rt3/Ticket/Display.html?id=42620 >
Both t/compilers/pge/p5regex/p5rx.t and
t/compilers/pge/p6regex/01-regex.t
are failing with the following error message:
t/compilers/pge/p5regex/p5rx.............Parrot VM: PANIC: Out of mem!
C file src/gc/memory.c, line 97
Parrot file (not available), line (not available)
We highly suggest you notify the Parrot team if you have not been working on
Parrot. Use parrotbug (located in parrot's root directory) or send an
e-mail to [EMAIL PROTECTED]
Include the entire text of this error message and the text of the script that
generated the error. If you've made any modifications to Parrot, please
describe them as well.
Version : 0.4.11-devel
Configured : Thu Apr 19 13:05:49 2007 GMT
Architecture: nojit
JIT Capable : No
Interp Flags: (no interpreter)
Exceptions : (missing from core)
Dumping Core...
dubious
Test returned status 0 (wstat 3, 0x3)
DIED. FAILED tests 399-960
Failed 562/960 tests, 41.46% okay (less 143 skipped tests: 255 okay,
26.56%)
The summaries for those tests read as follows:
Failed Test Stat Wstat Total Fail Failed List of Failed
t/compilers/pge/p5regex/p5rx.t 0 3 960 1124 117.08% 399-960
t/compilers/pge/p6regex/01-regex. 0 3 ?? ?? % ??
By further reducing the amount of memory available (with ulimit) I can make the
tests die a little earlier. It seems like parrot's memory footprint
keeps growing while processing the test file. I don't know if it's a
garbage collection issue or if pge is expected to take ever-growing
amounts of memory.
This is under Solaris 8/SPARC with Sun's cc compiler. I have just 128 MB
of RAM in this system.
This should be easily reproducible on other Unix-ish platforms: Just set
ulimit -v to some smaller value (e.g. 96 MB). Observe how the point of
failure moves around in the p5rx file as you increase or decrease the
available memory.
--
Andy Dougherty [EMAIL PROTECTED]
