Experiencing same memory leak problem on Fedora 8 Kernel 2.6.24.3-34 x86_64, glibc 2.7-2,
with FireFox 2.0.0.08, 2.0.0.10, 2.0.0.12, and 2.0.0.13
and AdobeReader 8.1.1 and 8.1.2
b Observations when running any version of FireFox:
*1-when reading a pdf file, System Monitor displays a new process called "ld-linux.so.2";
*2-when getting off the pdf file, process "ld-linux.so.2" remains active;
*3-when reading a new pdf file, another "ld-linux.so.2" is started;
*4-when closing FireFox, one or several "ld-linux.so.2" processes remain active and become runaway processes;
*5-these "ld-linux.so.2" runaway processes eat-up about 1MB per second until system freezes.
b Another observation:
*When starting Adobe Reader, System Monitor does not display "acroread", it displays "ld-linux.so.2"
Adobe Reader launcher uses a script called "acroread"; this script launches the binary either directly
or through "/lib/ld-linux.so.2".
b Further observations:
*1-In FireFox, when Adobe Reader is launched through "/lib/ld-linux.so.2", it becomes a runaway process.
*2-On the other hand, when Adobe Reader is launched directly,
]-System Monitor displays "acroread"
]-acroread always terminates as it supposed to do.
b Solutions:
* 1-add a symbolic link as follows:
]ln -s ld-linux.so.2 /lib/ld-lsb.so.3
*2-or install Package redhat-lsb as follows:
]yum install redhat-lsb
b Conclusion:
It appears that "/lib/ld-linux.so.2" is not handling the "term signal" received from FireFox when exiting a pdf page. When Adobe Reader is started directly, it does handle the "term signal" received from FireFox and terminates correctly.
b Outstanding Question:
Is "/lib/ld-linux.so.2" supposed to handle the "term signal"? If so, this is where the bug is because it does not. If not, why is it used to launch Adobe Reader?
Home my many hours of investigations can help someone.
b Note
Sorry. Problem is NOT entirely solved here! Still some memory leaks at times.
