Red Hat Bugzilla – Bug 180352
Large number of files in home directory causes OpenMotif crash
Last modified: 2007-11-30 17:07:23 EST
+++ This bug was initially created as a clone of Bug #144494 +++
Description of problem:
An OpenMotif application that creates a MessageBox with an information
icon crashes due to a segmentation fault when there are a large number
of files in the user's home directory.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Download attached test case files: Makefile and msg-box.c
2. Compile test case program:
3. Confirm that the test case works:
4. Create 4000 files in home directory:
$ sh -c 'for (( i=0; $i <= 4000; i=$i+1 )); do touch testfile.$i; done'
5. Try the test case again and see it crash:
Actual Results: Segmentation fault
Expected Results: Should not crash.
If I comment out line 15 in the test case program (the line that sets
the information icon for the message box), it does not crash. So perhaps
it is looking for the icon in the home directory or something.
The number of files needed in the home directory to cause it to crash
can vary. It seems to be dependent on the length of the file name. I
named the test files testfile.N. But if I make the names of the test
files longer then fewer test files are needed to get it to crash.
-- Additional comment from email@example.com on 2005-01-07 13:17 EST --
Created an attachment (id=109483)
Makefile for test case program
-- Additional comment from firstname.lastname@example.org on 2005-01-07 13:18 EST --
Created an attachment (id=109484)
Test case program
-- Additional comment from email@example.com on 2006-02-02 11:59 EST --
Created an attachment (id=124057)
Patch to solve this problem
Upstream motifzone fix which solves this problem.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.