Re: Performer 2.5 segfault on Linux Accelerated-X

New Message Reply Date view Thread view Subject view Author view

From: Tom Flynn (flynnt++at++engr.sgi.com)
Date: 03/20/2002 15:16:09


Hi there...

If the vidmode extension doesn't exist, what _should_ happen is that we
fall back to just setting the videorate variable to 60. The check can be
skipped by doing a setenv PFVIDEORATE 60 before running perfly.
let's get together off-line and see if we can get this problem
reproduced/fixed.

thanks for the report,
tom

On Wed, 20 Mar 2002, Michael Ginis wrote:

> Dear Performer users/devlopers,
>
> There have been reports that the Linux version of perfly distributed
> with Performer 2.5 segfaults almost immediately after startup. The
> problem is manifested as a core dump from one of the perfly threads,
> leaving the other thread (which appears to do the rendering) running
> in the background but inoperative. Sometimes the the perfly GUI is
> left visible on the screen, in other cases it never gets that far.
>
> After invesitagting, QA found that this happens only on certain Linux
> OS distributions with our Accelerated-X servers, which has our own
> accelerated OpenGL implementation and different extensions than
> XFree86/NVIDIA OpenGL implementations. By distribution I mean
> different versions of Slackware, Mandrake, etc...
>
> On most distributions perfly works with Accelerated-X, however on
> those distributions that it does not work we have not been able to
> isolate anythong wrong with Accelerated-X that would cause the crash,
> or anything special about those distributions which would explain why
> it crashes. We managed to get a stack trace out of perfly, which
> showed the last call on the stack to be 'pfChannel::computeStress'
> initiated by a 'pfFrame' call.
>
> We tried to reproduce the problem with XFree86/NVIDIA servers, but
> stock servers did not show this problem on the same distributions
> where perfly was crashing with Accelerated-X. However, one thing
> different between XFree86/NVIDIA and Accelerated-X is that Performer
> tries to query the refresh rate using the XFree86 VidMode extension,
> and perfly warns that this extension is missing with Accelerated-X.
> (Accelerated-X does not support this extension, because we have our
> own extension and library to query/set resolutions and rates, XiGMisc
> and XME).
>
> We removed the XFree86 VidMode extension from the XFree86/NVIDIA
> server and then perfly started to crash for XFree86/NVIDIA as well.
> So we think that there may be a problem in 'libpf', possibly related
> to an uninitialized variable or reading the refresh rate. We haven't
> been able to find sources for 'libpf', so we haven't been able to
> investigate further. We'd like find the problem, since a number of
> our customers use Performer. Thanks for any ideas or help.
>
> Sincerely,
>
> --
> Mike Ginis
> mginis++at++xig.com
> http://www.xig.com
> ------------------------------------------------------------------------
>
> -----------------------------------------------------------------------
> List Archives, Info, FAQ: http://www.sgi.com/software/performer/
> Open Development Project: http://oss.sgi.com/projects/performer/
> Submissions: info-performer++at++sgi.com
> Admin. requests: info-performer-request++at++sgi.com
> -----------------------------------------------------------------------
>

--
"Mongooses are famous for their snake-fighting ability, and are
 almost always victorious because of their speed, agility, and timing
 and also because of their thick coat."


New Message Reply Date view Thread view Subject view Author view

This archive was generated by hypermail 2b29 : Wed Mar 20 2002 - 15:16:17 PST

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