Re: [Chicken-janitors] #1045: [panic] out of memory - heap full while resizing - execution terminated (awful-picman)

[Chicken Trac]

#1045: [panic] out of memory - heap full while resizing - execution terminated
(awful-picman)
----------------------+-----------------------------------------------------
  Reporter:  mario    |       Owner:                                            
  
      Type:  defect   |      Status:  new                                       
  
  Priority:  major    |   Milestone:  4.9.0                                     
  
 Component:  unknown  |     Version:  4.8.x                                     
  
Resolution:           |    Keywords:  awful-picman, out of memory error, heap 
full
----------------------+-----------------------------------------------------

Comment(by alaric):

 I have a reproduction case for this using the Ugarit unit-test suite, too,
 if it helps. Basically, Ugarit runs a child process to manage actual
 storage operations, and talks to it via s-expressions over standard input
 and output. The test suites run fine, except for if I run the same
 sequence of operations as other tests use, but using an SHA hash rather
 than a Tiger one; this is a difference in the parent process, observable
 to the child process purely as the hash strings it is sent being different
 (with a different length, I note), but in that case, the child gives the
 same panic error message; but only after it's been sent the command to
 terminate itself cleanly. More details available upon request!

 Ugarit also suffers a problem (in the parent process this time) where some
 srfi-4 function complains that what it's being passed isn't a u8vector,
 but printing it out exactly before the srfi-4 call shows that it is, which
 also suggests that memory is being corrupted somehow. Maybe related.
 C-Keen is able to reproduce this, but I've not seen it myself.

 However, I do feel it is quite likely that Chicken has at least one
 underlying subtle memory corruption problem here!

 Previous mailing-list discussions on this and similar mysteries that look
 like memory corruption (I don't have the message ID, sorry) resulted in
 the idea of Felix adding optional logging hooks to the lowest-level
 runtime operations relating to garbage collection, if somebody else would
 write tools to process the logs, checking various complex invariants to
 see if an inconsistency can be found.

-- 
Ticket URL: <http://bugs.call-cc.org/ticket/1045#comment:2>
Chicken Scheme <http://www.call-with-current-continuation.org/>
Chicken Scheme is a compiler for the Scheme programming language.