| Summary: | kcachegrind fails with large PHP cachegrind file | ||
|---|---|---|---|
| Product: | [Developer tools] kcachegrind | Reporter: | Larry Crouch <larry> |
| Component: | general | Assignee: | Josef Weidendorfer <josef.weidendorfer> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | ||
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Debian stable | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Larry Crouch
2012-07-05 19:02:40 UTC
That's the same as bug 232470. It's an out-of-memory triggered by loading the huge file. Two work-arounds for the moment: (1) try to run a 64-bit kcachegrind (2) in libcore/fixcost.h, set the define for USE_FIXCOST to 0, and recompile. Even with 64-bit, your machine with 3 GB could probably will start heavy swapping. So (2) is better, as it will aggregate the profile information while loading, and memory requirements stay low. *** This bug has been marked as a duplicate of bug 232470 *** On Friday, July 06, 2012 04:11:31 you wrote:
> https://bugs.kde.org/show_bug.cgi?id=303073
>
> Josef Weidendorfer <josef.weidendorfer@gmx.de> changed:
>
> What |Removed |Added
> ---------------------------------------------------------------------------
> - Status|UNCONFIRMED |RESOLVED
> Resolution|--- |DUPLICATE
>
> --- Comment #1 from Josef Weidendorfer <josef.weidendorfer@gmx.de> ---
> That's the same as bug 232470.
> It's an out-of-memory triggered by loading the huge file.
>
> Two work-arounds for the moment:
> (1) try to run a 64-bit kcachegrind
> (2) in libcore/fixcost.h, set the define for USE_FIXCOST to 0, and
> recompile.
>
> Even with 64-bit, your machine with 3 GB could probably will start heavy
> swapping.
> So (2) is better, as it will aggregate the profile information while
> loading, and
> memory requirements stay low.
>
> *** This bug has been marked as a duplicate of bug 232470 ***
My apologies for the duplicate. My search was not good enough I guess. Thank
you for the information and work-around.
|