| Summary: | Crashes related Oxygen::TileSet::render | ||
|---|---|---|---|
| Product: | [Plasma] Oxygen | Reporter: | Georg Wittenburg <georg.wittenburg> |
| Component: | general | Assignee: | Hugo Pereira Da Costa <hugo.pereira.da.costa> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | crash | CC: | hugo.pereira.da.costa |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
Backtrace
2nd backtrace |
||
Created attachment 60298 [details]
2nd backtrace
Let me specify "no user interaction": I didn't click on anything, but I can't rule out any onMouseOver-like events. mmm. Floating point exception in QPainter. I just looked into QPainter.cpp code at the guilty lines mentionned by the crash. sx = qRound(sx) % qRound(sw); sy = qRound(sy) % qRound(sh); I guess either sw or sh (which are the pixmaps size) must be zero. Meaning. Invalid pixmap. I'll digg into the tileset code ... (this should not happen) PS: I do not think it is driver related. mmmm. That's not it.
QPainter, line 6696 checks for the validity of the pixmap.
if (!d->engine || pixmap.isNull() || r.isEmpty())
So no clue :(
After more time with this new laptop, I'm now pretty certain that it's an X or Intel i915 driver issue. Evidence is that large batch processes crash, but only when run from an X terminal window, not if run with X disabled. Sorry for the trouble. :) |
Created attachment 60297 [details] Backtrace Version: unspecified (using KDE 4.6.3) OS: Linux I've seen two crashes of Kontact and Dr. Konqi with Oxygen::TileSet::render featured prominently in the backtrace (see below). No user interaction took place with these applications immediately prior to the crash. This is a new laptop, so I don't rule out that it might be an X / driver issue. Reproducible: Sometimes