Qt4.6.2: X Errors nach Stunden mit abort

Alles rund um die Programmierung mit Qt
Antworten
nando
Beiträge: 321
Registriert: 28. Oktober 2004 13:16

Qt4.6.2: X Errors nach Stunden mit abort

Beitrag von nando »

Hi,

hat jemand eine Idee was es mit dieser Laufzeitfehlermeldung, die erst nach Stunden auftritt aufsich haben kann?


Folgende Umgebung:

* Qt 4.6.2
* SuSE Linux Enterprise 11
* NVIDIA Karte
* IceWM windowmanager


Error:

Code: Alles auswählen

X Error: BadIDChoice (invalid resource ID chosen for this connection) 14
  Major opcode: 55 (X_CreateGC)
  Resource id:  0x192d5a8
X Error: BadIDChoice (invalid resource ID chosen for this connection) 14
  Major opcode: 53 (X_CreatePixmap)
  Resource id:  0x192d5a9
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Extension:    155 (RENDER)
  Minor opcode: 4 (RenderCreatePicture)
  Resource id:  0x192d5a9
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode: 55 (X_CreateGC)
  Resource id:  0x192d5a9
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode: 72 (X_PutImage)
  Resource id:  0x192d5a9
X Error: BadGC (invalid GC parameter) 13
  Major opcode: 60 (X_FreeGC)
  Resource id:  0x192d5ab
X Error: RenderBadPicture (invalid Picture parameter) 181
  Extension:    155 (RENDER)
  Minor opcode: 8 (RenderComposite)
  Resource id:  0x192d5aa
X Error: RenderBadPicture (invalid Picture parameter) 181
  Extension:    155 (RENDER)
  Minor opcode: 7 (RenderFreePicture)
  Resource id:  0x192d5aa
X Error: BadPixmap (invalid Pixmap parameter) 4
  Major opcode: 54 (X_FreePixmap)
  Resource id:  0x192d5a9
X Error: BadIDChoice (invalid resource ID chosen for this connection) 14
  Major opcode: 53 (X_CreatePixmap)
  Resource id:  0x192d5b3
X Error: BadIDChoice (invalid resource ID chosen for this connection) 14
  Major opcode: 55 (X_CreateGC)
  Resource id:  0x192d5b4
...
...
X Error: RenderBadPicture (invalid Picture parameter) 181
  Extension:    155 (RENDER)
  Minor opcode: 6 (RenderSetPictureClipRectangles)
  Resource id:  0x192e370
X Error: RenderBadPicture (invalid Picture parameter) 181
  Extension:    155 (RENDER)
  Minor opcode: 5 (RenderChangePicture)
  Resource id:  0x192e370
X Error: RenderBadPicture (invalid Picture parameter) 181
  Extension:    155 (RENDER)
  Minor opcode: 10 (RenderTrapezoids)
  Resource id:  0x192e370
X Error: RenderBadPicture (invalid Picture parameter) 181
  Extension:    155 (RENDER)
  Minor opcode: 5 (RenderChangePicture)
  Resource id:  0x192e370
X Error: RenderBadPicture (invalid Picture parameter) 181
  Extension:    155 (RENDER)
  Minor opcode: 10 (RenderTrapezoids)
  Resource id:  0x192e370
X Error: RenderBadPicture (invalid Picture parameter) 181
  Extension:    155 (RENDER)
  Minor opcode: 5 (RenderChangePicture)
  Resource id:  0x192e370
X Error: BadGC (invalid GC parameter) 13
  Major opcode: 60 (X_FreeGC)
  Resource id:  0x192e3a6
X Error: BadGC (invalid GC parameter) 13
  Major opcode: 60 (X_FreeGC)
  Resource id:  0x192e3a5
X Error: RenderBadPicture (invalid Picture parameter) 181
  Extension:    155 (RENDER)
  Minor opcode: 5 (RenderChangePicture)
  Resource id:  0x192e370
X Error: BadPixmap (invalid Pixmap parameter) 4
  Major opcode: 56 (X_ChangeGC)
  Resource id:  0x192e36f
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode: 73 (X_GetImage)
  Resource id:  0x192e36f
QPainter::end: Painter ended with 3 saved states
Qt has caught an exception thrown from an event handler. Throwing
exceptions from an event handler is not supported in Qt. You must
reimplement QApplication::notify() and catch all exceptions there.

Qt has caught an exception thrown from an event handler. Throwing
exceptions from an event handler is not supported in Qt. You must
reimplement QApplication::notify() and catch all exceptions there.

terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc
start.sh: 10483 Aborted 

Gruss,
Nando
RavenIV
Beiträge: 267
Registriert: 21. Januar 2009 14:24
Wohnort: Waldshut

Beitrag von RavenIV »

Ich würde den Speicherverbrauch der Applikation über längere Zeit im Auge behalten.
Entweder manuell im Taskmanager oder den aktuell verbrauchten Speicher in ein logfile schreiben.
Hinweis: Memory-Leaks.
Linux, das längste Text-Adventure aller Zeiten
Antworten