After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 482142 - ***MEMORY-ERROR***: firestarter[6356]: GSlice: assertion failed: sinfo->n_allocated > 0
***MEMORY-ERROR***: firestarter[6356]: GSlice: assertion failed: sinfo->n_all...
Status: RESOLVED INCOMPLETE
Product: firestarter
Classification: Deprecated
Component: general
unspecified
Other All
: Normal critical
: ---
Assigned To: Tomas Junnonen
Tomas Junnonen
Depends on:
Blocks:
 
 
Reported: 2007-10-01 12:04 UTC by Stemp
Modified: 2009-12-17 17:12 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Stemp 2007-10-01 12:04:23 UTC
Steps to reproduce:
1. Start Firestarter GUI
2. Wait
3. 


Stack trace:
http://launchpadlibrarian.net/8733037/firestarter.0.crash
http://launchpadlibrarian.net/8108357/gdb-firestarter.txt
http://launchpadlibrarian.net/9088619/gdb-firestarter.txt

Other information:
From Ubuntu Launchpad Bug #120445
https://bugs.launchpad.net/ubuntu/+source/firestarter/+bug/120445

Version : 1.0.3-6ubuntu1
Comment 1 Floppyjoe 2007-12-23 07:27:02 UTC
This happens on my computers too on Ubuntu 7.10 OS.

Result of launching from terminal=
***MEMORY-ERROR***: firestarter[9437]: GSlice: assertion failed: sinfo->n_allocated > 0
Aborted (core dumped)
Comment 2 Floppyjoe 2007-12-23 08:21:00 UTC
Also when launched from terminal=
Segmentation fault (core dumped)

Comment 3 Carlos Medina 2008-02-28 22:29:22 UTC
I'm on with this same problem, every time I start Firestarter GUI from shell, it ends with the very same error.

***MEMORY-ERROR***: firestarter[21198]: GSlice: assertion failed: sinfo->n_allocated > 0

Comment 4 André Klapper 2009-08-09 20:25:52 UTC
If this is still an issue in a current version, please attach the stacktraces here.
--> NEEDINFO
Comment 5 André Klapper 2009-12-17 17:12:49 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!