[Bug 745247] New: bug in MALLOC_CHECK_ > 0 makes SublimeText2 crash
https://bugzilla.novell.com/show_bug.cgi?id=745247 https://bugzilla.novell.com/show_bug.cgi?id=745247#c0 Summary: bug in MALLOC_CHECK_ > 0 makes SublimeText2 crash Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: dmacvicar@suse.com QAContact: qa@suse.de Found By: --- Blocker: --- SublimeText2 build > 2165 crashes on openSUSE 12.1. Reported here: http://sublimetext.userecho.com/topic/93647-crash-right-at-startup-on-opensu... According to the author of SublimeText2, this is related to a glibc bug: http://sourceware.org/bugzilla/show_bug.cgi?id=1349 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=745247 https://bugzilla.novell.com/show_bug.cgi?id=745247#c1 Marcus Meissner <meissner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |meissner@suse.com --- Comment #1 from Marcus Meissner <meissner@suse.com> 2012-02-06 10:18:02 UTC --- we did release an aaa_base update that disables the default malloc memory checking btw, did you install all updates? also it is usually a bug in the application, not in glibc... ;) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=745247 https://bugzilla.novell.com/show_bug.cgi?id=745247#c2 --- Comment #2 from Duncan Mac-Vicar <dmacvicar@suse.com> 2012-02-06 11:31:45 UTC --- If you look at the upstream bug, it looks like the check is broken. In my laptop is working now. I guess one had to reboot for the update to take effect. Still this does not fix the check itself. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=745247 https://bugzilla.novell.com/show_bug.cgi?id=745247#c Marcus Meissner <meissner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |aj@suse.com |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=745247 https://bugzilla.novell.com/show_bug.cgi?id=745247#c3 --- Comment #3 from Andreas Jaeger <aj@suse.com> 2012-02-06 14:03:53 UTC --- This has been rejected upstream as a bug. For now, I suggest to not use malloc_usable_size. I'll followup upstream. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=745247 https://bugzilla.novell.com/show_bug.cgi?id=745247#c4 Andreas Jaeger <aj@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #4 from Andreas Jaeger <aj@suse.com> 2012-10-09 07:16:10 UTC --- The upstream bug is fixed. I'm backporting the fix to our glibc for Factory. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com