App 1.16

Author	Message
Martin P. Send message Joined: 21 Nov 07 Posts: 52 Credit: 1,756,052 RAC: 0	Message 1835 - Posted: 4 Mar 2008, 19:15:58 UTC Just finished the first work-units with (Mac) App 1.16. They validated o.k. However, the timing bug is still there: the timer goes to 100%, then restarts at 0 and goes back to 0.150%. At that point it suddenly jumps to 100% and uploads. ID: 1835 · Rating: 0 · rate: / Reply Quote

Stick Send message Joined: 8 Oct 07 Posts: 52 Credit: 6,004,147 RAC: 110	Message 1836 - Posted: 4 Mar 2008, 20:56:07 UTC - in response to Message 1835. Last modified: 4 Mar 2008, 21:07:13 UTC resultid=4566597 - This one just finished and validated (with Windows v1.16). Like the report below, my unit went to 100%, restarted at 0% and then went to 0.154% before finishing. It also reported: "Memory Leaks Detected". EDIT: resultid=4566605 - DITTO for this one (from my other host). Just finished the first work-units with (Mac) App 1.16. They validated o.k. However, the timing bug is still there: the timer goes to 100%, then restarts at 0 and goes back to 0.150%. At that point it suddenly jumps to 100% and uploads. ID: 1836 · Rating: 0 · rate: / Reply Quote

Jayargh Send message Joined: 8 Oct 07 Posts: 289 Credit: 3,690,838 RAC: 0	Message 1837 - Posted: 4 Mar 2008, 21:25:37 UTC - in response to Message 1836. resultid=4566597 - This one just finished and validated (with Windows v1.16). Like the report below, my unit went to 100%, restarted at 0% and then went to 0.154% before finishing. It also reported: "Memory Leaks Detected". EDIT: resultid=4566605 - DITTO for this one (from my other host). Just finished the first work-units with (Mac) App 1.16. They validated o.k. However, the timing bug is still there: the timer goes to 100%, then restarts at 0 and goes back to 0.150%. At that point it suddenly jumps to 100% and uploads. Travis said in another thread that 1.16 is just a rollback to 1.13 with those bugs ,,,thats why ID: 1837 · Rating: 0 · rate: / Reply Quote

Travis Volunteer moderator Project administrator Project developer Project tester Project scientist Send message Joined: 30 Aug 07 Posts: 2046 Credit: 26,480 RAC: 0	Message 1838 - Posted: 4 Mar 2008, 21:40:07 UTC - in response to Message 1837. resultid=4566597 - This one just finished and validated (with Windows v1.16). Like the report below, my unit went to 100%, restarted at 0% and then went to 0.154% before finishing. It also reported: "Memory Leaks Detected". EDIT: resultid=4566605 - DITTO for this one (from my other host). Just finished the first work-units with (Mac) App 1.16. They validated o.k. However, the timing bug is still there: the timer goes to 100%, then restarts at 0 and goes back to 0.150%. At that point it suddenly jumps to 100% and uploads. Travis said in another thread that 1.16 is just a rollback to 1.13 with those bugs ,,,thats why We should have 1.17 out tonight -- I'm just waiting on dave to compile some different binaries and sign the files. ID: 1838 · Rating: 0 · rate: / Reply Quote

Stick Send message Joined: 8 Oct 07 Posts: 52 Credit: 6,004,147 RAC: 110	Message 1841 - Posted: 4 Mar 2008, 23:45:22 UTC - in response to Message 1837. Last modified: 4 Mar 2008, 23:49:14 UTC Travis said in another thread that 1.16 is just a rollback to 1.13 with those bugs ,,,thats why Thanks! I saw the "News" note but, obviously, I didn't understand it. (Hopefully, I won't be reporting the same issues for v1.17.) ID: 1841 · Rating: 0 · rate: / Reply Quote

Jim Wilkins Send message Joined: 1 Jan 08 Posts: 40 Credit: 1,676,165 RAC: 0	Message 1889 - Posted: 5 Mar 2008, 14:03:04 UTC Should I abort 32 bit Windows 1.16 tasks? Jim ID: 1889 · Rating: 0 · rate: / Reply Quote