chromium-browser crashed with SIGSEGV in base::debug::TaskAnnotator::RunTask()

Bug #1424816 reported by wgroiss
This bug report is a duplicate of:  Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
chromium-browser (Ubuntu)
New
Undecided
Unassigned

Bug Description

Chromium was opened with 7 tabs. I've read my incoming emails and clicked on the following link:

http://mobil.derstandard.at/1369361554177/Ein-Schuljahr-in-Finnland?fb_action_ids=635888953091271&fb_action_types=og.recommends&fb_ref=article&fb_source=other_multiline&action_object_map=%5B540396502672909%5D&action_type_map=%5B%22og.recommends%22%5D&action_ref_map=%5B%22article%22%5D

Cromium opened an 8th tab with the correct link, but - additionally - showed this bug, too.

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: chromium-browser 40.0.2214.111-0ubuntu1.1121
ProcVersionSignature: Ubuntu 3.18.0-14.15-generic 3.18.7
Uname: Linux 3.18.0-14-generic x86_64
ApportVersion: 2.16.1-0ubuntu2
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Mon Feb 23 21:34:45 2015
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/chromium-browser/chromium-browser
InstallationDate: Installed on 2015-01-18 (36 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150117)
ProcCmdline: chromium-browser\ --type=gpu-process\ --channel=3053.0.337261371\ --supports-dual-gpus=false\ --gpu-driver-bug-workarounds=1,12,14,39\ --disable-accelerated-video-decode\ --gpu-vendor-id=0x8086\ --gpu-device-id=0x0166\ --gpu-driver-vendor\ --gpu-driver-versi
SegvAnalysis:
 Segfault happened at: 0x7f56772c11f8: movl $0x1337,0x0
 PC (0x7f56772c11f8) ok
 source "$0x1337" ok
 destination "0x0" (0x00000000) not located in a known VMA region (needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: chromium-browser
StacktraceTop:
 ?? () from /usr/lib/chromium-browser/libs/libcontent.so
 base::debug::TaskAnnotator::RunTask(char const*, char const*, base::PendingTask const&) () from /usr/lib/chromium-browser/libs/libbase.so
 base::MessageLoop::RunTask(base::PendingTask const&) () from /usr/lib/chromium-browser/libs/libbase.so
 base::MessageLoop::DeferOrRunPendingTask(base::PendingTask const&) () from /usr/lib/chromium-browser/libs/libbase.so
 base::MessageLoop::DoDelayedWork(base::TimeTicks*) () from /usr/lib/chromium-browser/libs/libbase.so
Title: chromium-browser crashed with SIGSEGV in base::debug::TaskAnnotator::RunTask()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
modified.conffile..etc.default.chromium.browser: [deleted]
mtime.conffile..etc.chromium.browser.default: 2015-01-25T07:00:39.618771

Revision history for this message
wgroiss (wolfgang-groiss-gmx) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1402523, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

information type: Private → Public
tags: removed: need-amd64-retrace
Revision history for this message
wgroiss (wolfgang-groiss-gmx) wrote : Re: [Bug 1424816] Re: chromium-browser crashed with SIGSEGV in base::debug::TaskAnnotator::RunTask()

Hello!
I wanted to have a look up at:
https://bugs.launchpad.net/bugs/1402523

But i can't find it. I only find a lot of bugs, which are marked as
duplicate, but i cannot find the "orignial bug".

Regards

Wolfgang Groiss

Am 2015-02-23 um 22:01 schrieb Apport retracing service:

> *** This bug is a duplicate of bug 1402523 ***
> https://bugs.launchpad.net/bugs/1402523
>
> Thank you for taking the time to report this crash and helping to make
> this software better. This particular crash has already been reported
> and is a duplicate of bug #1402523, so is being marked as such. Please
> look at the other bug report to see if there is any missing information
> that you can provide, or to see if there is a workaround for the bug.
> Additionally, any further discussion regarding the bug should occur in
> the other report. Please continue to report any other bugs you may
> find.
>
> ** Attachment removed: "CoreDump.gz"
> https://bugs.launchpad.net/bugs/1424816/+attachment/4325743/+files/CoreDump.gz
>
> ** Attachment removed: "Disassembly.txt"
> https://bugs.launchpad.net/bugs/1424816/+attachment/4325745/+files/Disassembly.txt
>
> ** Attachment removed: "ProcMaps.txt"
> https://bugs.launchpad.net/bugs/1424816/+attachment/4325748/+files/ProcMaps.txt
>
> ** Attachment removed: "ProcStatus.txt"
> https://bugs.launchpad.net/bugs/1424816/+attachment/4325749/+files/ProcStatus.txt
>
> ** Attachment removed: "Registers.txt"
> https://bugs.launchpad.net/bugs/1424816/+attachment/4325750/+files/Registers.txt
>
> ** Attachment removed: "Stacktrace.txt"
> https://bugs.launchpad.net/bugs/1424816/+attachment/4325753/+files/Stacktrace.txt
>
> ** Attachment removed: "ThreadStacktrace.txt"
> https://bugs.launchpad.net/bugs/1424816/+attachment/4325754/+files/ThreadStacktrace.txt
>
> ** This bug has been marked a duplicate of private bug 1402523
>
> ** Information type changed from Private to Public
>
> ** Tags removed: need-amd64-retrace
>

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
  • Duplicate of a private bug Remove

Other bug subscribers

Remote bug watches

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