BT 0.84

[fred]

History tab view does not honor the chosen time format, "Elapsed Time" still shows some times like : 
AQUA@home    1.14 IQUANA (mt1)    iq64A2_281006a_2_164_0    01d,01:40:42 (03d,19:03:24)    10-31-10  02:36    10-31-10  02:38    4.00C    Reported: OK (u)

Feature request:  Configurable column placement in the History tab.

This is not a time format:  01d,01:40:42 (03d,19:03:24)

[Beyond]

History tab view does not honor the chosen time format, "Elapsed Time" still shows some times like : 
AQUA@home    1.14 IQUANA (mt1)    iq64A2_281006a_2_164_0    01d,01:40:42 (03d,19:03:24)    10-31-10  02:36    10-31-10  02:38    4.00C    Reported: OK (u)

Feature request:  Configurable column placement in the History tab.

This is not a time format:  01d,01:40:42 (03d,19:03:24)

You mean it's not supposed to conform to our time format HHH:MM:SS choice in BoincTasks Settings/View?

[fred]

You mean it's not supposed to conform to our time format HHH:MM:SS choice in BoincTasks Settings/View?

Noted as a bug.

[John McLeod VII]

I have been having trouble with 2 major problems recently.

1)  BT 0.84 and a few previous versions occasionally post an Öut of Memory" warning.  Several of these are posted and the program then crashes.
2)  Random crashes.

I am willing to try to help debug the problem.

[Pepo]

1)  BT 0.84 and a few previous versions occasionally post an "Out of Memory" warning.  Several of these are posted and the program then crashes.

I am willing to try to help debug the problem.

Have yo maybe noticed the real/maximum memory requirements of the process at the moment? (Task Manager or Process Explorer or the like?) Whether it really tried to allocate that much...

[Corsair]

I have been having trouble with 2 major problems recently.

1)  BT 0.84 and a few previous versions occasionally post an Öut of Memory" warning.  Several of these are posted and the program then crashes.
2)  Random crashes.

I am willing to try to help debug the problem.

same has happened to me since some versions ago, mainly in x32 version,
but seen twice or three times in x64 too.

about temperature graphic in x32 version, same updated TT to version 3.0
(all computers x32 & x64), vertical scale and temperature graph not available
for the x32 machine.

[fred]

I have been having trouble with 2 major problems recently.

1)  BT 0.84 and a few previous versions occasionally post an Öut of Memory" warning.  Several of these are posted and the program then crashes.
2)  Random crashes.

I am willing to try to help debug the problem.

Memory handling is done by the OS, when there is not enough memory, the program will halt/crash.
What is:
OS type,  32/64bit , memory, BOINC version.
I'm implementing some changes in V 0.85 to address some suspected issues.
But this may leave 0.85, more alpha than beta. As I already made hundreds of small changes from one type to another. Any small mistake I make, may result in a crash....

[fred]

about temperature graphic in x32 version, same updated TT to version 3.0
(all computers x32 & x64), vertical scale and temperature graph not available
for the x32 machine.

It's a BT problem, I think, it may be resolved in V 0.85. If not.... an extra debugging flag should give me some more info, about what's going on.

[glennaxl]

Waiting to run tasks is showing cpu %. Shouldn't this be null (-), as its not running?

Also if you suspend this waiting to run task, its still showing cpu %.

[fred]

Waiting to run tasks is showing cpu %. Shouldn't this be null (-), as its not running?

Also if you suspend this waiting to run task, its still showing cpu %.

It will go to the average cpu% known. When I change that to 0, you get no info at all, about how a the CPU % was.

[glennaxl]

Waiting to run tasks is showing cpu %. Shouldn't this be null (-), as its not running?

Also if you suspend this waiting to run task, its still showing cpu %.

It will go to the average cpu% known. When I change that to 0, you get no info at all, about how a the CPU % was.

How about hiding it by a simple color change  maching the background.

[glennaxl]

another one:

when a tasks is suspended and you abort it, status still says suspended.

[Pepo]

Waiting to run tasks is showing cpu %. Shouldn't this be null (-), as its not running?
Also if you suspend this waiting to run task, its still showing cpu %.

It will go to the average cpu% known. When I change that to 0, you get no info at all, about how a the CPU % was.

How about hiding it by a simple color change  maching the background.

I vote for keeping the average% visible - the task's Status and optional whole row highlighting is about whether it runs.

[fred]

when a tasks is suspended and you abort it, status still says suspended.

Interesting, on the bug list.

[Beyond]

when a tasks is suspended and you abort it, status still says suspended.

Interesting, on the bug list.

Just tried this on 0.84 and it aborts properly for me.  Doesn't always show the aborted WU in History however.