cpufreqd assert failure: *** glibc detected *** /usr/sbin/cpufreqd: free(): invalid pointer: 0x0000000001870bb0 ***

Bug #952764 reported by Csaba Gerencsér
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cpufreqd (Ubuntu)
New
Undecided
Unassigned

Bug Description

This happens after login, when the indicator-cpufreq is starting.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: cpufreqd 2.4.2-1
ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9
Uname: Linux 3.2.0-18-generic x86_64
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
AssertionMessage: *** glibc detected *** /usr/sbin/cpufreqd: free(): invalid pointer: 0x0000000001870bb0 ***
CrashCounter: 1
Date: Wed Mar 7 08:29:19 2012
ExecutablePath: /usr/sbin/cpufreqd
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
ProcCmdline: /usr/sbin/cpufreqd -f /etc/cpufreqd.conf
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=hu_HU.UTF-8
Signal: 6
SourcePackage: cpufreqd
StacktraceTop:
 __libc_message (do_abort=2, fmt=0x7f5e793d3250 "*** glibc detected *** %s: %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:201
 malloc_printerr (action=3, str=0x7f5e793d0201 "free(): invalid pointer", ptr=<optimized out>) at malloc.c:5007
 sysfs_read_attribute () from /lib/libsysfs.so.2
 read_value () from /usr/lib/cpufreqd/cpufreqd_acpi.so
 read_int () from /usr/lib/cpufreqd/cpufreqd_acpi.so
Title: cpufreqd assert failure: *** glibc detected *** /usr/sbin/cpufreqd: free(): invalid pointer: 0x0000000001870bb0 ***
UpgradeStatus: Upgraded to precise on 2012-03-11 (0 days ago)
UserGroups:

Revision history for this message
Csaba Gerencsér (eezeemen) 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 #733507, 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.

visibility: private → public
visibility: private → public
tags: removed: need-amd64-retrace
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.