miro.real crashed with SIGSEGV

Bug #717865 reported by Mathieu Marquer
98
This bug affects 1 person
Affects Status Importance Assigned to Milestone
miro (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: miro

Crashed on startup after taking 100% CPU during a few seconds.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: miro 3.5.1-1ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-3.30-generic 2.6.38-rc4
Uname: Linux 2.6.38-3-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
CrashCounter: 1
Date: Sat Feb 12 21:12:03 2011
ExecutablePath: /usr/bin/miro.real
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110131)
InterpreterPath: /usr/bin/python2.7
ProcCmdline: /usr/bin/python2.7 /usr/bin/miro.real
ProcEnviron:
 LANGUAGE=fr_FR.UTF-8:fr:en_GB:en
 LANG=fr_FR.UTF-8
 LC_MESSAGES=fr_BE.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x3cc759e5c5: movl $0x0,(%rdx)
 PC (0x3cc759e5c5) ok
 source "$0x0" ok
 destination "(%rdx)" (0xbbadbeef) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: miro
StacktraceTop:
 ?? () from /usr/lib/libwebkitgtk-1.0.so.0
 ?? () from /usr/lib/libwebkitgtk-1.0.so.0
 ?? () from /usr/lib/libwebkitgtk-1.0.so.0
 ?? () from /usr/lib/libwebkitgtk-1.0.so.0
 ?? () from /usr/lib/libwebkitgtk-1.0.so.0
Title: miro.real crashed with SIGSEGV
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Mathieu Marquer (slasher-fun) wrote :
Revision history for this message
Mathieu Marquer (slasher-fun) wrote :

Added gdb with some symbols. Relevant part :

Program received signal SIGSEGV, Segmentation fault.
0x0000003cc759e5c5 in WTF::OSAllocator::reserveAndCommit (
    bytes=<value optimized out>, usage=<value optimized out>,
    writable=<value optimized out>, executable=<value optimized out>)
    at ../Source/JavaScriptCore/wtf/OSAllocatorPosix.cpp:85
85 ../Source/JavaScriptCore/wtf/OSAllocatorPosix.cpp: Aucun fichier ou dossier de ce type.
 in ../Source/JavaScriptCore/wtf/OSAllocatorPosix.cpp

visibility: private → public
visibility: public → private
Revision history for this message
Mathieu Marquer (slasher-fun) wrote :

Mmm... Would that be a duplicate of bug 710582 ?

visibility: private → public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.