kerneloops crashed with SIGSEGV in _int_malloc()

[JONNALAGADDA Srinivas]

kerneloops crashed with SIGSEGV in _int_malloc().

Too non-specific. Last action performed was scrolling down a Web page in Chrome, using mouse. The system continues to operate normally; so does Chrome!

SYSTEM DETAILS:

Description: Ubuntu Trusty Tahr (development branch)
Release: 14.04

kerneloops:
  Installed: (none)
  Candidate: 0.12+git20090217-3ubuntu6
  Version table:
     0.12+git20090217-3ubuntu6 0
        500 http://in.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: kerneloops-daemon 0.12+git20090217-3ubuntu6
ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5
Uname: Linux 3.13.0-14-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
Date: Thu Mar 20 12:15:34 2014
ExecutablePath: /usr/sbin/kerneloops
InstallationDate: Installed on 2014-02-25 (22 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140222)
ProcCmdline: /usr/sbin/kerneloops
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
SegvAnalysis:
 Segfault happened at: 0x7f63a45f5231 <_int_malloc+2337>: mov %r13,(%rax,%r13,1)
 PC (0x7f63a45f5231) ok
 source "%r13" ok
 destination "(%rax,%r13,1)" (0xa3030303137e268) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: kerneloops
StacktraceTop:
 _int_malloc (av=0x7f63a4933760 <main_arena>, bytes=16000) at malloc.c:3740
 __GI___libc_malloc (bytes=16000) at malloc.c:2891
 ?? ()
 ?? ()
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: kerneloops crashed with SIGSEGV in _int_malloc()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

[Apport retracing service (apport)]

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 #1287351, 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.