Bug 884741

Summary:	Coqide: "Fatal error: out of memory."
Product:	[Fedora] Fedora	Reporter:	Gwendal <ezwen-redhatbugzilla>
Component:	coq	Assignee:	Alan Dunn <amdunn>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	18	CC:	amdunn, dwheeler, fedora-ocaml-list, loganjerry, rjones
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-12-13 16:23:00 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Gwendal 2012-12-06 16:19:39 UTC

Description of problem:
coqide does not work, and displays an error message instead: "Fatal error: out of memory."


Version-Release number of selected component (if applicable):
Nom                 : coq-coqide
Architecture        : x86_64
Version             : 8.4
Révision            : 1.fc18


How reproducible: Always on my system.


Steps to Reproduce:
1. # yum install coq-coqide
2. # coqide
  
Actual results:
Error message: "Fatal error: out of memory."

Expected results:
CoqIDE main window should appear.

Additional info:
I've submitted a bug report on Coq bug tracker as well: https://coq.inria.fr/bugs/show_bug.cgi?id=2943

Comment 1 Jerry James 2012-12-07 00:01:40 UTC

Thanks for the report, Erwan.  I will look into it.

Comment 2 Jerry James 2012-12-08 00:04:24 UTC

Interestingly, this does *not* happen on Rawhide, where coqide behaves normally.  
GDB shows this:

#0  mmap64 () at ../sysdeps/unix/syscall-template.S:81
#1  0x0000003f1bc7df3e in sysmalloc (av=0x7ffff0000020, nb=259407338535940144) at malloc.c:2304
#2  _int_malloc (av=0x7ffff0000020, bytes=<optimized out>) at malloc.c:3786
#3  0x0000003f1bc7f428 in __GI__libc_malloc (bytes=259407338535940128) at malloc.c:2877
#4  0x000000000066ba7f in ?? ()

followed by lots more unknown stack frames.  So some ocaml function is making a call to malloc() to request a ridiculous number of bytes ... but only on F-18.  Hmmmmmm.....

Comment 3 Jerry James 2012-12-11 21:55:43 UTC

I suspect this is bug 877128.  I will mark this bug as a duplicate if someone can confirm that.

Comment 4 Jerry James 2012-12-13 16:23:00 UTC


*** This bug has been marked as a duplicate of bug 877128 ***