Version: (using KDE 3.5.2, compiled sources) Compiler: gcc version 3.4.5 OS: Linux (i686) release 2.6.16.5 The fireworks screensaver crash when glib library is greater than 2.8.6. I've checked glib up to 2.10.2 version and the last working one with fireworks is 2.8.6. Many apps require minimum glib 2.10 so I have to choose between fireworks screensaver or new apps. Could you update fireworks to be compatible with glib 2.10? The fireworks screensaver displays error on console from which X was launched: ***MEMORY-ERROR***: [4332]: GSlice: failed to allocate 248 bytes (alignment: 256): Bad argument
The bug is in glib-2. I think they have already put out a new version that works. Can you confirm?
The last one is glib-2.10.2 available since April 2006. This glib is available from http://ftp.gnome.org/pub/GNOME/platform/2.14/2.14.1/sources/ Still fireworks screensaver does not work. I asked on gnome bugzilla if they can confirm glib bug. Will wait will see.
The problem is that arts crashes with newer glib versions. This is a bug in arts and not in glib. But it doesn't seem to happen on all platforms. I run it with glic-2.4, gcc-4.1 and glib2-2.10.2. This is the error I get: ***MEMORY-ERROR***: [1033]: GSlice: failed to allocate 248 bytes (alignment: 256): Invalid argument
The last memory-bugless glib is glib-2.9.0 The first glib with memory-bug is glib-2.9.1 I opened similar bug in gnome bugzilla. Hope this will be fixed by gnome or KDE or both teams. It looks for me the KDE arts and fireworks have to be updated.
Here is changelog 2.9.0 to 2.9.1 (scroll down to end of page): http://mail.gnome.org/archives/gnome-announce-list/2005-December/msg00009.html This could be the reason for memory-error (from changelog): * Memory management - The slice allocator is implemented [Tim Janik] - g_slice_free_chain() has been renamed to g_slice_free_chain_with_offset() [Tim, Behdad Esfahbod] - Mem chunks are deprecated [Matthias Clasen] * New API: - GList and GSList now have sort functions which take an extra user data argument [Martyn Russell]
Well I managed to fix this problem. I compiled KDE myself and optimized kdelibs using --enable-fast-malloc=full. This in combination with glib>=2.9.1 causes these problems. The problems are not in arts but in kdelibs (which also contain an arts part). This is the same problem as bugs 124460 and 120285. This would also explain why it doesn't happen on all distros with glib>=2.9.1 (gentoo for example disables fast-malloc). So the fix would be not to use --enable-fast-malloc when compiling the packages (this is off by default). The glib version doesn't matter anymore.
Which parts of KDE uses fast malloc with errors? Browsing compilation logs I see that only modules kdelibs and kdesdk tells about use of fast malloc. If I compile kdelibs only without fast malloc the problem will gone away?
Yep for me that works. Compiling kdelibs without malloc support fixes this problem.
As far as I know fast malloc is deprecated and should not be used. Adding Lubos to CC since he can hopefully provide further insight.
I confirm. Removing --enable-fast-malloc from configure options fixed bug.
artsd and kdesktop also fail to work normally with this flag enabled. You can now safely close PR124460. It's a pity getting such a response from KDE developers.
*** Bug 124460 has been marked as a duplicate of this bug. ***