| Summary: | PHP: crash in KDevelop::DUChainBase::makeDynamic / makeDataPrivate - possibly OOM | ||
|---|---|---|---|
| Product: | [Applications] kdevelop | Reporter: | Eugen <eugen.mayer> |
| Component: | Language Support: PHP | Assignee: | kdevelop-bugs-null |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | insomniac |
| Priority: | NOR | Keywords: | triaged |
| Version First Reported In: | 4.2.0 | ||
| Target Milestone: | 4.2.0 | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Eugen
2011-01-28 13:24:51 UTC
for the record: [19:01] <milian> ugh [19:01] <milian> is it reproducible on start? [19:01] <EugenMayer> AFAIK i remember it even happend on my kde 4.5 installation ( a completly fresh installation ) ~5 months ago when i tried KDE once again [19:01] <milian> i.e.: can you run it through valgrind? [19:02] <EugenMayer> and finaly gone back to gnome again due the whole pim-stuff :/ [19:02] <EugenMayer> milian: hmm, currenlty it does not crash. [19:02] <EugenMayer> valgrind ~ kcachgrind? [19:02] <milian> also: when it crashes - do you see anything on the cli? [19:02] <milian> like an out-of-memory assert [19:03] <milian> EugenMayer: if you ever reproduce it run kdev like this "valgrind --track-origins=yes --num-callers=25 kdevelop" [19:03] <EugenMayer> hmm, i cant really remember. when it crashes on the next project, i will try to check the cli and: if you find a way to reproduce, please tell me what project it is (i.e. if possible send me a tarball) *** Bug 291347 has been marked as a duplicate of this bug. *** Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |