possible bug : choosing Einstein's "show graphics" options freezes the calculation
25 Jan 2005 11:17:17 UTC
Topic 187344
(moderation:
Today I noticed a strange effect on my client:
while normally Einstein@home is working in the background, choosing the "show graphics" option causes the process to freeze. I get a normal graphics window, which shows the starsphere normally moving. The target cross doesn't move, and on the boinc client window the work time counter no longer increments. When I close the graphics window, the work time counter restarts to increment.
possible bug : choosing Einstein's "show graphics" options freez
)
> Today I noticed a strange effect on my client:
>
> while normally Einstein@home is working in the background, choosing the "show
> graphics" option causes the process to freeze. I get a normal graphics window,
> which shows the starsphere normally moving. The target cross doesn't move, and
> on the boinc client window the work time counter no longer increments. When I
> close the graphics window, the work time counter restarts to increment.
>
[EDIT] It's not the same, Yours : have you set "leave appl. in memmory" yes, than you see the graphic from the paused WU.[/EDIT]
Seems to be the same as I had . See this
[EDIT] Meanwhile It stopped, Will detach this machine. [/EDIT]
Waiting for replies
friendly littleBouncer
> > Today I noticed a strange
)
> > Today I noticed a strange effect on my client:
> >
> > while normally Einstein@home is working in the background, choosing the
> "show
> > graphics" option causes the process to freeze. I get a normal graphics
> window,
> > which shows the starsphere normally moving. The target cross doesn't
> move, and
> > on the boinc client window the work time counter no longer increments.
> When I
> > close the graphics window, the work time counter restarts to increment.
> >
> [EDIT] It's not the same, Yours : have you set "leave appl. in memmory" yes,
> than you see the graphic from the paused WU.[/EDIT]
> Seems to be the same as I had . See href="https://einsteinathome.org/%3Ca%20href%3D"http://einsteinathome.org/node/187342">http://einsteinathome.org/node/187342">this[/url]
>
> [EDIT] Meanwhile It stopped, Will detach this machine. [/EDIT]
>
> Waiting for replies
> friendly littleBouncer
>
No, I just checked on my general preferences, and I have "no" set for
the option "leave appl. in memory". Moreover, this is in the general
preferences, not in the project-specific ones, and since a few minutes
ago Seti@home has just returned into execution, I have been able to see
that this problem doesn't happen with SETI@home. So I think it's tightly related with Einstein@home...
For how long did you keep the
)
For how long did you keep the graphics window open? I would assume that the process counter would increase _very_ slowly, but not actually freeze.
To me this looks like you have a graphics card without (or non-working) hardware-accelerated OpenGL and the OpenGL graphics done by the CPU eats up all the cycles, leaving nothing for the worker thread ("crunching").
BM
BM
> For how long did you keep
)
> For how long did you keep the graphics window open? I would assume that the
> process counter would increase _very_ slowly, but not actually freeze.
>
> To me this looks like you have a graphics card without (or non-working)
> hardware-accelerated OpenGL and the OpenGL graphics done by the CPU eats up
> all the cycles, leaving nothing for the worker thread ("crunching").
>
> BM
>
That seems to be the problem also for this
If you are an "graphic-card-expert" I have some Q's. (better in german or by e-mail contact me at : , please)