that's a ffmpeg lib issue
==27091== Invalid write of size 1
==27091==at 0x4028623: memset (mc_replace_strmem.c:493)
==27091==by 0x13CB999B: avcodec_default_get_buffer (string3.h:85)
==27091== Address 0x10307ebf is 0 bytes after a block of size 15 alloc'd
==27091==at 0x4024EFA: memalig
that's a ffmpeg lib issue
==27091== Invalid write of size 1
==27091==at 0x4028623: memset (mc_replace_strmem.c:493)
==27091==by 0x13CB999B: avcodec_default_get_buffer (string3.h:85)
==27091== Address 0x10307ebf is 0 bytes after a block of size 15 alloc'd
==27091==at 0x4024EFA: memalig
** Changed in: nautilus (Ubuntu)
Status: Incomplete => New
--
nautilus crashed with SIGSEGV in memset()
https://bugs.launchpad.net/bugs/339854
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop
after long googling i was able to exit nautilus and open it with valgrind
(gconf-editor->show_desktop->disable and then start valgrind)
valgrind in attachment
** Attachment added: "valgrind"
http://launchpadlibrarian.net/23631536/valgrind.log
--
nautilus crashed with SIGSEGV in memset()
http
that's because you have a nautilus already running, move the binary away
and make a small nautilus wrapper which calls the real binary under
valgrind
** Changed in: nautilus (Ubuntu)
Status: New => Incomplete
--
nautilus crashed with SIGSEGV in memset()
https://bugs.launchpad.net/bugs/339
As I said I cannot obtain valgrind for nautilus:
ne...@nexem-desktop:~$ G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v
--tool=memcheck --leak-check=full --num-callers=40 --log-file=valgrind.log
nautilus
ne...@nexem-desktop:~$
valgrind is exiting just after nautilus start
** Changed in:
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a valgrind log following the
instructions at https://wiki.ubuntu.com/Valgrind and attach the file to
the bug report. This will greatly help us in tracking down your problem.
** Changed in: naut
ok, adding backtrace, from attach to already running program
** Attachment added: "backtrace"
http://launchpadlibrarian.net/23629804/gdb-nautilus.txt
--
nautilus crashed with SIGSEGV in memset()
https://bugs.launchpad.net/bugs/339854
You received this bug notification because you are a member
I can't attach backtrace and valgrind, because I don't know how to track new
threads:
(gdb) run
Starting program: /usr/bin/nautilus
[Thread debugging using libthread_db enabled]
[New Thread 0xb6efe750 (LWP 20786)]
[New Thread 0xb6c44b90 (LWP 20791)]
Program exited normally. - gdb exits after nau
