+2
Not a bug
Duncan Mac-Vicar Prett 6 years ago • updated by Jon Skinner 5 years ago 4
Sublime text would not start but crash. I am stuck in version 2139 as the "last working one" (released).

Backtrace posted at http://www.sublimetext.com/forum/viewtopic.php?f=3&t=4557&p=20648&hilit=crash#p20648

Cleaning up the config worked for 2165, but does not for 2172 (except for 32bit, where it starts with a clean config). Still in all cases it crashes when closing the application as well. All startup backtraces have the same first lines:

======= Backtrace: =========
/lib64/libc.so.6(+0x74c06)[0x7f5822dc1c06]
./sublime_text(_ZN12memory_arena5clearEv+0x20)[0x51bf70]
./sublime_text[0x759444]
./sublime_text(_ZN13SyntaxManager6reloadEv+0x7e1)[0x75a051]
./sublime_text(_ZN13SyntaxManager4initEP15settings_loaderP11menu_loader+0x25)[0x75baf5]
./sublime_text(_Z12skyline_initP9catalogueP14px_file_systemP15settings_loaderP11menu_loader+0xfd)[0x6a906d]


Answer

Answer
Not a bug
This is a bug in glibc: http://sourceware.org/bugzilla/show_bug.cgi?id=1349
Workaround: run sublimetext with MALLOC_CHECK_=0
MALLOC_CHECK_=1 works as well of course, and prints the warning:

*** glibc detected *** ./sublime_text: free(): invalid pointer: 0x0000000001748650 ***

Level 2 and above abort.
Answer
Not a bug
This is a bug in glibc: http://sourceware.org/bugzilla/show_bug.cgi?id=1349
From https://bugzilla.novell.com/show_bug.cgi?id=745247#c3


 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.

I can confirm this bug on Fedora 17 x32 and sublime 2219.

here is full text: http://stackoverflow.com/questions/13921665/sublimetext-always-crash-after-start