Testing V 7.15

[fred]

New: Portuguese.
Fixed: Didn't always scale right when moving back in time.

This is the release candidate.

[Pepo]

Yesterday at evening, while looking for the reason, why did my computer require that much virtual memory, I've noticed that the top glutton was TThrottle - at some moment during previous 22 hours it required to allocate 2 GB  memory to fulfill some secret task:

   

Fred, could you please take the code under microscope, which part could be that greedy? I've no idea whether this amount was also filled with some data (and doubt it), as the Peak Working Set was only 150 MB.
If necessary for any debugging, the process is still running here, luckily inside its 30 MB of memory.

[fred]

Yesterday at evening, while looking for the reason, why did my computer require that much virtual memory, I've noticed that the top glutton was TThrottle - at some moment during previous 22 hours it required to allocate 2 GB  memory to fulfill some secret task:
Fred, could you please take the code under microscope, which part could be that greedy? I've no idea whether this amount was also filled with some data (and doubt it), as the Peak Working Set was only 150 MB.
If necessary for any debugging, the process is still running here, luckily inside its 30 MB of memory.

I found the cause, forgot the add a max buffer length, for a string that is less than 5 bytes long.
It caused a buffer to be assigned for an undefined amount, but only for a millisecond or so.
I'm not sure if the memory is assigned and processed by the system.
Fixed in 7.16 soon.

[Pepo]

I found the cause, forgot the add a max buffer length, for a string that is less than 5 bytes long.
It caused a buffer to be assigned for an undefined amount, but only for a millisecond or so.
I'm not sure if the memory is assigned and processed by the system.

Good catch!
Then I suppose the memory request was just approved, but no more memory blocks were written, as there was no demand for it.

[tlsi2000]

I just downloaded and installed the version 7.15 onto two XP 64 machines.  Each machine is totally different, but the  behavior is the same.
Once  TThrottle starts up, it seems to find the BoincTasks correctly, and then about 5-8 seconds in, it aborts itself and exits gracefully..

BoincTasks is at v1.56

On both these machines, TThrottle v5 and v6 ran correctly.
On the Win7 machine (again a totally different configuration) the TThrottle v7.15 is running correctly.

Looking for answers, and ways to help...
tlsi2000

--------------
For a starting point, this is a copy of Log Tab of one machine (just able to get it before it dropped out)
--------------

20 October 2013 - 18:51:55 Driver installed properly. Driver Version: 2.4 XP
20 October 2013 - 18:51:55 Driver regulator: not supported (9052)
20 October 2013 - 18:51:56 Program version: 7.16,64Bit
Microsoft Windows XP Professional x64 Edition Service Pack 2 (build 3790)
Language: User: 1033 (ENU), System: 1033 (ENU), Selected: 0 () Used: 1033 (ENU)
NVidia
LogicalGpu: 0, PhysicalGpuCount: 1
LogicalGpu: 1, PhysicalGpuCount: 1

GeForce GT 240,Pos: 0, ID: 212013278 | 110956766 | 3235 | busId: 5 | busSlot: 5
GeForce GTX 560 Ti,Pos: 1, ID: 301994206 | 890573912 | 4608 | busId: 4 | busSlot: 4
Total PhysicalGpuCount: 2

nvidia: found 2 logical devices
nvidia: found 2 physical devices
NrGpu: 0,  SensorNr: 0, TCount 1 - TMax: 127,  Temp: 61 nvidia: Temperature 61 °C, max Temperature 127 °C
NrGpu: 1,  SensorNr: 0, TCount 1 - TMax: 127,  Temp: 65 nvidia: Temperature 65 °C, max Temperature 127 °C

nvidia: GeForce GT 240, GeForce GTX 560 Ti
AMD_ATI
Try to load Library: atiadlxx.dll
Try to load Library: atiadlxy.dll
Library not found

Vendor ID: AuthenticAMD
Vendor ID: AMD
HighestIntegerValue: 00000001 - Processor Signature: 00040F33
Misc. info: 00020800
Feature Flags1 00002001
Feature Flags2 178BFBFF

Processor: AMD Athlon(tm) 64 X2 Dual Core Processor 6000+                 
Processor: Family: Fh, Model: 43, Stepping: 3
Processor: Revision: JH-F3, Revision: F
Processor: Socket: AM2, Type: Athlon(tm) 64 X2 Dual-Core
Processor: Max Die (Tjunction) Temperature: 70.0 °C
\t\tThe real Max Die (Tjunction) temperature is not this value
\t\tThis value is for calculating the temperature ONLY
\t\tMax Die (Tjunction) is normally about Max Case + 5C
Processor: Max Case Temperature: 70.0 °C, Max Power: 0.0 W

Core Temperature: 50 °C, Raw Data: 631920
631920,631920,641920,641920,641920,641920,641920,641920,641920,641920,64
1920,641920,641920,641920,641920,641920,641920,641920,641920,641920,6419
20,641920,641920,651920,651920,651920,651920,651920,651920,651920,651920
,651920,|0;1;ffffffff;ffffffff;1;1;1;1;1;1;1;1;1;1;1;1;1;1;1;1;1;1;1;1;1
;1;1;1;1;1;1;1;

Status: 1, Bus: 0, Device: 24, Function: 2, F2x94, DRAM CHR:7410006B   
Status: 1, Bus: 0, Device: 24, Function: 2, F2x64, HTC:00000000   
Status: 1, Bus: 0, Device: 24, Function: 2, F2xE8, NBridge:00001719   
Status: 1, Bus: 0, Device: 24, Function: 3, F3xE4, Temperature (F):DE611994   
Status: 1, Bus: 0, Device: 24, Function: 3, F3xA4, Temperature:00000000   
Status: 0, Bus: 0, Device: 31, Function: 2, F2x94, DRAM CHR:00000000   
Status: 0, Bus: 0, Device: 31, Function: 2, F2x64, HTC:00000000   
Status: 0, Bus: 0, Device: 31, Function: 2, F2xE8, NBridge:00000000   
Status: 0, Bus: 0, Device: 31, Function: 3, F3xE4, Temperature (F):00000000   
Status: 0, Bus: 0, Device: 31, Function: 3, F3xA4, Temperature:00000000   
This Processor has 2 cores and  1 temperature sensors.
Regulator threads used for the CPU: 1

BOINC:
asteroidsathome.net_boinc
einstein.phys.uwm.edu
milkyway.cs.rpi.edu_milkyway
setiathome.berkeley.edu

You can help by reading www.efmer.eu/boinc/faq.html How can I help!
Select the send EMail button,or copy everything in this logging window and mail it to me!
boinc[At]efmer[Dot]eu. We use this information to improve this product.

Gpu's found: 2, bus slots used by BOINC: 4 5 -1 -1 -1 -1 -1 -1
TThrottle is using GPU device position: 1 0 -1 -1 -1 -1 -1 -1

20 October 2013 - 18:52:06 Number of matching Programs (Processes): 5
CPU: period_search_10210_windows_x86_64__sse3.exe, PID: 2488, Threads: 3
CPU: period_search_10210_windows_x86_64__sse3.exe, PID: 3432, Threads: 3
GPU: einsteinbinary_brp4g_1.39_windows_intelx86__brp4g-cuda32-nv301.exe, PID: 2440, Threads: 4
GPU: einsteinbinary_brp4g_1.39_windows_intelx86__brp4g-cuda32-nv301.exe, PID: 3508, Threads: 4
GPU: setiathome_7.00_windows_intelx86__cuda42.exe, PID: 3240, Threads: 4
---------------------------------------------------------------------------------------------------------------------   2 0 3 0
20 October 2013 - 18:52:06 Connected with BOINC client
20 October 2013 - 18:52:06 Number of matching Programs (Processes): 5

[fred]

I just downloaded and installed the version 7.15 onto two XP 64 machines.  Each machine is totally different, but the  behavior is the same.
Once  TThrottle starts up, it seems to find the BoincTasks correctly, and then about 5-8 seconds in, it aborts itself and exits gracefully..

First try the latest Beta, if that doesn't solve the problem.

Try http://efmer.com/forum/index.php?topic=338.0 Crash files from TThrottle and BoincTasks.

[fred]

Can you make a copy from both machines.
The entire log folder: C:\Users\username\AppData\Roaming\eFMer\TThrottle\log
And send it to me.

Next delete the entire log folder and try starting TThrottle again.

[tlsi2000]

Fred...

I have uploaded the files via the WeTransfer site.

There are four files, 2 each from each of the two machines.
The BEFORE files are those as the logs were after the last attempt a couple days ago.
Then I deleted the files in the Log directory, and started TThrottle.
It stayed up for maybe 15 seconds,.
The AFTER files are from this clean start of each machine.

Thanks for the response.
Let me know if there is anything else I can do at this end.

Thanks,
tlsi2000

[fred]

I still don't know what's causing the crashes.

But 7.21 is another try.

Drop in the xml (by email) next to the exe, normally Program Files\eFMer\TThrottle
Create a folder C:\logging
There is where the xml point the log files.
The xml generates additional info and sets the logging in the debug mode.
Give me the new crash files and the logging.