Closed Bug 500163 Opened 16 years ago Closed 16 years ago

seamonkey-2.0b1pre crash with "munmap_chunk(): invalid pointer"

Categories

(SeaMonkey :: General, defect)

x86_64
Linux
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 493541

People

(Reporter: sagiben, Unassigned)

Details

(Keywords: crash)

User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.11) Gecko/2009060200 SUSE/3.0.11-5.2 Firefox/3.0.11 Build Identifier: http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/2009-06-14-00-comm-1.9.1/seamonkey-2.0b1pre.en-US.linux-x86_64.tar.bz2 Hi, The first time this issue happened was when I closed seamonkey-2.0b1pre and started seamonkey-1.1.16 application by mistake. In order to use the beta again I closed the released version and tried to start to beta version but it crashed and I couldn't start it (the beta version) anymore. The only thing that solved this issue was to restart my machine. Reproducible: Always Steps to Reproduce: 1. start seamonkey beta 2. close all it's windows 3. start seamonkey released version 4. close all it's windows 5. start seamonkey beta version Expected Results: *** glibc detected *** /data/seamonkey/seamonkey-bin: munmap_chunk(): invalid pointer: 0x00007fe409371980 *** ======= Backtrace: ========= /lib64/libc.so.6[0x7fe40cd43118] /lib64/libnss_nis.so.2(_nss_nis_getpwnam_r+0x101)[0x7fe4055a5381] /lib64/libnss_compat.so.2[0x7fe4057ae16b] /lib64/libnss_compat.so.2(_nss_compat_getpwnam_r+0x227)[0x7fe4057ae437] /lib64/libc.so.6(getpwnam_r+0xed)[0x7fe40cd6fa7d] /usr/lib64/libglib-2.0.so.0[0x7fe41016486c] /usr/lib64/libglib-2.0.so.0(g_get_user_name+0xad)[0x7fe410165fad] /usr/lib64/libgnomeui-2.so.0[0x7fe408e34b0d] /usr/lib64/libgobject-2.0.so.0(g_type_create_instance+0x46a)[0x7fe4103e915a] /usr/lib64/libgobject-2.0.so.0[0x7fe4103cd6fb] /usr/lib64/libgobject-2.0.so.0(g_object_newv+0x253)[0x7fe4103cdd33] /usr/lib64/libgobject-2.0.so.0(g_object_new_valist+0x327)[0x7fe4103ce887] /usr/lib64/libgobject-2.0.so.0(g_object_new+0xcc)[0x7fe4103ce9cc] /usr/lib64/libgnomeui-2.so.0(gnome_client_new_without_connection+0x12)[0x7fe408e34682] /usr/lib64/libgnomeui-2.so.0[0x7fe408e35890] /usr/lib64/libgnome-2.so.0(gnome_program_preinit+0x196)[0x7fe408545346] /usr/lib64/libgnome-2.so.0[0x7fe40854627b] /usr/lib64/libgnome-2.so.0(gnome_program_initv+0x2d)[0x7fe40854658d] /usr/lib64/libgnome-2.so.0(gnome_program_init+0xe4)[0x7fe408546684] /data/seamonkey/seamonkey-bin[0x44a1af] /data/seamonkey/seamonkey-bin[0x4440e0] /data/seamonkey/seamonkey-bin[0x441801] /lib64/libc.so.6(__libc_start_main+0xe6)[0x7fe40cced586] /data/seamonkey/seamonkey-bin[0x441639] ======= Memory map: ======== 00400000-014b9000 r-xp 00000000 08:13 95270529 /data/seamonkey/seamonkey-bin 016b8000-016f3000 rw-p 010b8000 08:13 95270529 /data/seamonkey/seamonkey-bin 016f3000-0170c000 rw-p 016f3000 00:00 0 [heap] Machine info : # uname -a Linux nin 2.6.27.23-0.1-default #1 SMP 2009-05-26 17:02:05 -0400 x86_64 x86_64 x86_64 GNU/Linux # cat /etc/SuSE-release openSUSE 11.1 (x86_64) VERSION = 11.1
This looks like it's actually http://bugzilla.novell.com/show_bug.cgi?id=503151 and not our bug (openSUSE did some changes to glibc nss that don't play nice with our jemalloc memory management).
Blocks: 499736
Keywords: crash
Version: unspecified → Trunk
Serge, bug 499736 doesn't mention memory management or a stack with glibc stuff on top, and we didn't have jemalloc on 1.1.x, so I'm pretty sure those are very different things.
No longer blocks: 499736
I have to following glibc rpms installed : glibc-2.9-2.11.1 glibc-32bit-2.9-2.11.1 glibc-devel-2.9-2.11.1 glibc-devel-32bit-2.9-2.11.1 glibc-i18ndata-2.9-2.11.1 glibc-info-2.9-2.11.1 glibc-locale-2.9-2.11.1 glibc-locale-32bit-2.9-2.11.1
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.