PF Fatal/Internal(2): Assertion failed: _pfCurrentPipe

From: hans-peter.hofer++at++ruag.com
Date: 09/03/2001 01:43:40

• Next message: Bram Stolk: "Alternative solution for Performer 2.4 vs glibc2.2"
• Previous message: B. Grollmann: "FireGL 1 probs."
• Next in thread: Yair Kurzion: "Re: PF Fatal/Internal(2): Assertion failed: _pfCurrentPipe"
• Reply: Yair Kurzion: "Re: PF Fatal/Internal(2): Assertion failed: _pfCurrentPipe"

Hi Performers

I have a Performer visual application which is running quite good. But
sometimes, the application breaks with the following message:

PF Fatal/Internal(2): Assertion failed:
_pfCurrentPipe->pf_getFrameCount() != frameCount || frameCount == 0 in
../../../lib/libpf/pfProcess.C at line 6305

My system:

Onyx2 IR2
512MB RAM
2 RM9
IRIX 6.5.11
Performer 2.4

Can anybody give me a hint what's going on here?

Thanks

Hans-Peter

        Hans-Peter Hofer
        Senior Software Engineer

        RUAG Electronics
        Stauffacherstrasse 65
        Postfach
        CH-3000 Bern 22

        Tel. +41 31 32 47280
        Fax. +41 31 32 45679
        E-Mail hans-peter.hofer++at++ruag.com
        URL www.ruag.com

        Die SE Schweizerische Elektronikunternehmung AG tritt ab 1.5.01
unter dem neuen Namen RUAG Electronics auf.

• Next message: Bram Stolk: "Alternative solution for Performer 2.4 vs glibc2.2"
• Previous message: B. Grollmann: "FireGL 1 probs."
• Next in thread: Yair Kurzion: "Re: PF Fatal/Internal(2): Assertion failed: _pfCurrentPipe"
• Reply: Yair Kurzion: "Re: PF Fatal/Internal(2): Assertion failed: _pfCurrentPipe"

This archive was generated by hypermail 2b29 : Mon Sep 03 2001 - 01:44:17 PDT

This message has been cleansed for anti-spam protection. Replace '++at++' in any mail addresses with the '@' symbol.