Summary: | full CPU use when printing with CUPS-pdf, make damaged pdf file and then crash | ||
---|---|---|---|
Product: | [Applications] okular | Reporter: | lordmax <lordmax> |
Component: | general | Assignee: | Okular developers <okular-devel> |
Status: | RESOLVED NOT A BUG | ||
Severity: | crash | CC: | aacid, andresbajotierra, guilhermecervantes |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Unlisted Binaries | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
lordmax
2010-02-26 14:34:03 UTC
- Does the application crash again if you repeat the situation you described ? - Was some application using a lot of memory ? I wonder if it could be related to bug 196207. Regards I'll don't know if my problem can be associated to 196207 but I'll Hoe it. ^__^ The application does not crash every time with the same file and only some file had the problem. Approssimatively okular crash 3 on 5 times on the same file. Two process had great memory and process use: okular and gs (of cups-pdf) Thanks *** Bug 248738 has been marked as a duplicate of this bug. *** Can you still reproduce this behaviour? If you can, can you please install debugging symbols so your backtraces make sense? Thanks for caring about Okular :-) Sorry. It was two years and three SO ago. ^___^ I know it was long time ago, but your answer doesn't answer my question: Can you still reproduce this behaviour? No, I'm on a totally different OS and Kernel. I cant' reproduce it in any way User can't reproduce anymore nor can we. |