Summary: | Crash after long startup - NFSed images | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Stephen <stephen> |
Component: | Database-Media | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | caulier.gilles |
Priority: | NOR | ||
Version: | 1.9.0 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 2.3.0 |
Description
Stephen
2011-09-30 11:21:33 UTC
Memory allocation fails when listing a directory in QDir::entryInfoList. This would usually indicate out-of-memory condition, or rather a memory request which cannot be fulfilled. How many files are involved? Just under 6000. I get 15 secs of network traffic, cpu goes 100% then over the next few minutes the memory is all used up (2G). I will try on a machine with more memory. Tried with a machine with 8G and got this: KGlobal::locale::Warning your global KLocale is being recreated with a valid main component instead of a fake component, this usually means you tried to call i18n related functions before your main component was created. You should not do that since it most likely will not work QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is still in use, all queries will cease to work. terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc KCrash: Application 'digikam' crashing... KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit sock_file=/home/stephen/.kde/socket-cherub/kdeinit4__0 Warning: connect() failed: : No such file or directory KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi directly QSocketNotifier: Invalid socket 29 and type 'Read', disabling... <unknown>: Fatal IO error 9 (Bad file descriptor) on X server :0.0. Then indeed something is eating memory, and there is no good reason for that. If it worked with previous linux distros and same digikam version, chances are this is a bug somewhere in the system stack (Qt, file system, NFS driver) Upgraded to Ubuntu 11.10 and problems has gone. Thanks. |