Rosetta 4.1+ and 4.2+

Message boards : Number crunching : Rosetta 4.1+ and 4.2+

To post messages, you must log in.

Previous · 1 . . . 7 · 8 · 9 · 10 · 11 · 12 · 13 . . . 31 · Next

AuthorMessage
Sid Celery

Send message
Joined: 11 Feb 08
Posts: 1660
Credit: 30,548,225
RAC: 24,384
Message 94809 - Posted: 19 Apr 2020, 1:36:04 UTC - in response to Message 94792.  

I would think that it means they really need to see some of these extreme models completed. That all models might take a long time. Your scenario with early models completed and then one long one doesn't sound like the reason one would make the change described.

Rest assured that my experience with the project has always been that model runtimes and the consistency of model runtimes improves with updates to the specific protocols. But, in the meantime, extending the watchdog sounds like the fastest way for them to get some results.

{edit}
I don't mean to sound like I am refuting any of the desirable attributes of WUs that Sid mentioned. The Project Team is very aware of the desirability of checkpoints, fast consistent model runtimes, and etc. The fact that they chose to extend the watchdog to 10 hours really tells me that we're down to either do this, or don't get the data you need to continue your COVID study. I'm confident it will not be a permanent change.

If you guys are confident that it <is> an especially long-running first decoy that's going through, then fine.

I mean, it really <doesn't> look like that from where I'm sitting, but what I think and where I'm sitting doesn't count. It's just that we've never seen that here before.
ID: 94809 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Profile [VENETO] boboviz

Send message
Joined: 1 Dec 05
Posts: 1392
Credit: 5,784,791
RAC: 5,155
Message 94844 - Posted: 19 Apr 2020, 8:30:10 UTC - in response to Message 94793.  

(Task linked below) First time I ran it, it went over 24 hours, got to 99.4%, and then for other reasons I rebooted my machine. The same task after reboot reset to 0% and started over. I let it run 12+ hours the second time, and it was exhibiting the same behavior. I quit Boinc and relaunched, and again the same task reset to 0% and started over. I aborted it. Now it's on a Android machine, we'll see if it goes anywhere.

Aborted task: https://boinc.bakerlab.org/rosetta/result.php?resultid=1151472990

I spoke too early for me
After 20hs i killed this (at 99,1%): 1153761018
ID: 94844 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Profile Tom M

Send message
Joined: 20 Jun 17
Posts: 80
Credit: 2,243,090
RAC: 0
Message 94868 - Posted: 19 Apr 2020, 12:46:50 UTC

So are these extremely long run times only showing up on the "686" tasks?

Tom
Help, a tagline is missing..... Help, a tagline is......... Help, a........ Hel.....
ID: 94868 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Profile pschoefer

Send message
Joined: 3 Apr 09
Posts: 10
Credit: 6,927,553
RAC: 1,298
Message 94871 - Posted: 19 Apr 2020, 13:49:08 UTC

I have two of those monster 12v1n_* tasks that have been running on my old i7 980X for more than 2 days now (tasks 1152001896 and 1151897536). The graphics output says "Stage: unknown", "Model: 2 Step: 0", and has all energies and RMSDs at 0.

CPU time is close to elapsed time, and while there were no checkpoints that BOINC is aware of, there are two files in the respective slot directories that are modified every few minutes: rng.state.gz and a <task name>_check.txt. The latter file contains a lot of lines like "LAST x SUCCESS 0", where x is incrementing (now at 1200 and 1960). This leaves me with the impression that there is still something happening, which is why I hesitated to abort the tasks so far. Does anyone know what those files mean? I'd hate to abort the tasks after more than two days, but the deadline is approaching rapidly and I also do not want to waste even more time if there is no chance that these tasks may finish sometime in the foreseeable future.
ID: 94871 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Profile Grant (SSSF)

Send message
Joined: 28 Mar 20
Posts: 977
Credit: 10,608,788
RAC: 23,050
Message 94875 - Posted: 19 Apr 2020, 14:06:09 UTC - in response to Message 94868.  

So are these extremely long run times only showing up on the "686" tasks?
There are no 686 Tasks. Just as Seti doesn't have CPU or GPU Tasks.
A Rosetta Task is processed by whatever application is allocated to it.
Grant
Darwin NT
ID: 94875 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Millenium

Send message
Joined: 20 Sep 05
Posts: 68
Credit: 184,283
RAC: 0
Message 94876 - Posted: 19 Apr 2020, 14:08:30 UTC

After 2 days let's see what happens, maybe they will eventually complete!
ID: 94876 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
xii5ku

Send message
Joined: 29 Nov 16
Posts: 13
Credit: 12,625,298
RAC: 0
Message 94877 - Posted: 19 Apr 2020, 14:18:54 UTC - in response to Message 94189.  

On April 12 Grant (SSSF) wrote:
As it is, all present 64bit hardware & operating systems can handle 32bit applications-
I recently set up a new Linux box, but it didn't pull in any 32-bit compatibility libraries. I guess I need to install an arbitrary 32-bit-only application first, in order to prepare this box for BOINC projects which, unlike Rosetta@home, have Linux x86-32 applications but no x86-64 application.


On April 12 Grant (SSSF) wrote:
and their performance is on par with the 64bit ones.
This is not precisely correct. The AMD64 (EM64T) mode has a larger register file than IA-32 mode, and a few other improvements. On the other hand, 64-bit wide addresses make for a larger cache footprint. But the former positive effect supposedly often outweighs the latter negative effect.

But I don't have an idea how much Rosetta is impacted by one or the other. Probably to a negligible extent, compared with performance differences between workunits just due to different proteins analysed. So from this perspective, your argument that both versions are on par may be correct here in practice.

GCC and Linux can make use of a special mode, called "x32 ABI", in which the computer runs in AMD64 (EM64T) mode with the larger register file and all the other enhancements, but has applications use only 32 bits wide addresses with their lower cache footprint and limited virtual address space. But this is not mainstream, and AFAIK not used by any BOINC based project.
ID: 94877 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Mod.Sense
Volunteer moderator

Send message
Joined: 22 Aug 06
Posts: 4018
Credit: 0
RAC: 0
Message 94888 - Posted: 19 Apr 2020, 15:32:25 UTC - in response to Message 94871.  
Last modified: 19 Apr 2020, 15:46:08 UTC

pschoefer, unfortunately, I have not seen enough reports on these to give advice. But I can tell you that at the end of each model, a checkpoint is recorded, and output is produced. So if you are on model 2 now, it means some of the work has been preserved.

How much memory are these tasks using? How many hours of CPU have they received? What is your runtime preference set to?

Edit: Another report on a 12v1n_ task running over two days.

My suggestion: the maximum CPU time a WU could be configured to run would be the 36 hour maximum runtime preference plus the new 10 hour watchdog. 46 hours of CPU is less than the 2 days you are showing. So I would have to take that as evidence that it is not running normally and should be aborted.
Rosetta Moderator: Mod.Sense
ID: 94888 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Profile pschoefer

Send message
Joined: 3 Apr 09
Posts: 10
Credit: 6,927,553
RAC: 1,298
Message 94893 - Posted: 19 Apr 2020, 15:45:25 UTC - in response to Message 94888.  

How much memory are these tasks using? How many hours of CPU have they received? What is your runtime preference set to?

RAM usage is quite low, only ~100 MB. CPU time is now close to 57 hours and 52 hours. Target runtime is set to default.
ID: 94893 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Mod.Sense
Volunteer moderator

Send message
Joined: 22 Aug 06
Posts: 4018
Credit: 0
RAC: 0
Message 94895 - Posted: 19 Apr 2020, 15:47:27 UTC - in response to Message 94893.  

See my edit to my previous reply.
Rosetta Moderator: Mod.Sense
ID: 94895 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Admin
Project administrator

Send message
Joined: 1 Jul 05
Posts: 5553
Credit: 0
RAC: 0
Message 94905 - Posted: 19 Apr 2020, 16:52:28 UTC

These 12v1n_ are obviously having some issues. It's rare considering how many jobs were submitted but definitely an issue. These are cyclic peptide jobs so they have a small memory footprint but I'm guessing by random chance there may be situations where the trajectory keeps going for a while due to filtering criteria, but that's just an initial hunch. I'll have to talk to the researcher who ran these jobs and look specifically at the code and process to see what exactly is causing this. I already sent an email and we will start a discussion about this issue and a possible fix for the near future. I suggest aborting these jobs if they continue to run past your run time setting. Sorry for any inconvenience.
ID: 94905 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Profile pschoefer

Send message
Joined: 3 Apr 09
Posts: 10
Credit: 6,927,553
RAC: 1,298
Message 94914 - Posted: 19 Apr 2020, 17:37:54 UTC - in response to Message 94905.  

Thanks for your replies, I aborted the tasks.
ID: 94914 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Profile Beyond
Avatar

Send message
Joined: 30 May 06
Posts: 2
Credit: 8,464,861
RAC: 0
Message 94930 - Posted: 19 Apr 2020, 19:14:10 UTC - in response to Message 94905.  

These 12v1n_ are obviously having some issues. It's rare considering how many jobs were submitted but definitely an issue. These are cyclic peptide jobs so they have a small memory footprint but I'm guessing by random chance there may be situations where the trajectory keeps going for a while due to filtering criteria, but that's just an initial hunch. I'll have to talk to the researcher who ran these jobs and look specifically at the code and process to see what exactly is causing this. I already sent an email and we will start a discussion about this issue and a possible fix for the near future. I suggest aborting these jobs if they continue to run past your run time setting. Sorry for any inconvenience.

Looks like all the 12v1n WUs were just aborted by the server. This happened regardless of whether the WUs were already running. Posted for info in case anyone was wondering...
ID: 94930 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
JohnDK
Avatar

Send message
Joined: 6 Apr 20
Posts: 21
Credit: 1,043,481
RAC: 0
Message 94934 - Posted: 19 Apr 2020, 19:48:09 UTC

Yes had 2 12v1n WUs canceled, one of which had run for over 100.000 secs...
ID: 94934 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Sid Celery

Send message
Joined: 11 Feb 08
Posts: 1660
Credit: 30,548,225
RAC: 24,384
Message 94941 - Posted: 19 Apr 2020, 20:32:33 UTC - in response to Message 94930.  

These 12v1n_ are obviously having some issues. It's rare considering how many jobs were submitted but definitely an issue. These are cyclic peptide jobs so they have a small memory footprint but I'm guessing by random chance there may be situations where the trajectory keeps going for a while due to filtering criteria, but that's just an initial hunch. I'll have to talk to the researcher who ran these jobs and look specifically at the code and process to see what exactly is causing this. I already sent an email and we will start a discussion about this issue and a possible fix for the near future. I suggest aborting these jobs if they continue to run past your run time setting. Sorry for any inconvenience.

Looks like all the 12v1n WUs were just aborted by the server. This happened regardless of whether the WUs were already running. Posted for info in case anyone was wondering...

Yup - seen that here too
ID: 94941 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Profile Grant (SSSF)

Send message
Joined: 28 Mar 20
Posts: 977
Credit: 10,608,788
RAC: 23,050
Message 94967 - Posted: 20 Apr 2020, 6:01:50 UTC

Dodgy WU or just a glitch? Done plenty of others in that series with no issues.

Junior_HalfRoid_design4_COVID-19_SAVE_ALL_OUT_IGNORE_THE_REST_8rk5cy8c_914738_3_0

<core_client_version>7.6.33</core_client_version>
<![CDATA[
<message>
Incorrect function.
 (0x1) - exit code 1 (0x1)
</message>
<stderr_txt>
command: projects/boinc.bakerlab.org_rosetta/rosetta_4.15_windows_x86_64.exe -run:protocol jd2_scripting -parser:protocol jhr_boinc_v3.xml @flags -in:file:silent Junior_HalfRoid_design4_COVID-19_SAVE_ALL_OUT_IGNORE_THE_REST_8rk5cy8c.silent -in:file:silent_struct_type binary -silent_gz -mute all -out:file:silent_struct_type binary -out:file:silent default.out -in:file:boinc_wu_zip Junior_HalfRoid_design4_COVID-19_SAVE_ALL_OUT_IGNORE_THE_REST_8rk5cy8c.zip @Junior_HalfRoid_design4_COVID-19_SAVE_ALL_OUT_IGNORE_THE_REST_8rk5cy8c.flags -nstruct 10000 -cpu_run_time 28800 -watchdog -boinc:max_nstruct 1000 -checkpoint_interval 120 -database minirosetta_database -in::file::zip minirosetta_database.zip -boinc::watchdog -run::rng mt19937 -constant_seed -jran 1403217
Starting watchdog...
Watchdog active.
Starting watchdog...
Watchdog active.

ERROR: Assertion `copy_pose.size() == native.size()` failed. MSG:the reference pose must be the same size as the working pose
ERROR:: Exit from: ......srcprotocolsprotein_interface_designfiltersRmsdFilter.cc line: 323
BOINC:: Error reading and gzipping output datafile: default.out
13:05:06 (6696): called boinc_finish(1)

</stderr_txt>
]]>

Grant
Darwin NT
ID: 94967 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Tomcat雄猫

Send message
Joined: 20 Dec 14
Posts: 136
Credit: 3,592,999
RAC: 3,970
Message 95004 - Posted: 20 Apr 2020, 18:39:45 UTC - in response to Message 94967.  
Last modified: 20 Apr 2020, 18:40:55 UTC

Dodgy WU or just a glitch? Done plenty of others in that series with no issues.

Junior_HalfRoid_design4_COVID-19_SAVE_ALL_OUT_IGNORE_THE_REST_8rk5cy8c_914738_3_0

<core_client_version>7.6.33</core_client_version>
<![CDATA[
<message>
Incorrect function.
 (0x1) - exit code 1 (0x1)
</message>
<stderr_txt>
command: projects/boinc.bakerlab.org_rosetta/rosetta_4.15_windows_x86_64.exe -run:protocol jd2_scripting -parser:protocol jhr_boinc_v3.xml @flags -in:file:silent Junior_HalfRoid_design4_COVID-19_SAVE_ALL_OUT_IGNORE_THE_REST_8rk5cy8c.silent -in:file:silent_struct_type binary -silent_gz -mute all -out:file:silent_struct_type binary -out:file:silent default.out -in:file:boinc_wu_zip Junior_HalfRoid_design4_COVID-19_SAVE_ALL_OUT_IGNORE_THE_REST_8rk5cy8c.zip @Junior_HalfRoid_design4_COVID-19_SAVE_ALL_OUT_IGNORE_THE_REST_8rk5cy8c.flags -nstruct 10000 -cpu_run_time 28800 -watchdog -boinc:max_nstruct 1000 -checkpoint_interval 120 -database minirosetta_database -in::file::zip minirosetta_database.zip -boinc::watchdog -run::rng mt19937 -constant_seed -jran 1403217
Starting watchdog...
Watchdog active.
Starting watchdog...
Watchdog active.

ERROR: Assertion `copy_pose.size() == native.size()` failed. MSG:the reference pose must be the same size as the working pose
ERROR:: Exit from: ......srcprotocolsprotein_interface_designfiltersRmsdFilter.cc line: 323
BOINC:: Error reading and gzipping output datafile: default.out
13:05:06 (6696): called boinc_finish(1)

</stderr_txt>
]]>



Had same error on a similar WU.
Mine is called Junior_HalfRoid_design4_cart_COVID-19_SAVE_ALL_OUT_IGNORE_THE_REST_3qm4ib8m_913396_3_0

In my case, the error cropped up after restarting.

<core_client_version>7.16.5</core_client_version>
<![CDATA[
<message>
Incorrect function.
 (0x1) - exit code 1 (0x1)</message>
<stderr_txt>
command: projects/boinc.bakerlab.org_rosetta/rosetta_4.15_windows_x86_64.exe -run:protocol jd2_scripting -parser:protocol jhr_boinc_v3_cart.xml @flags -in:file:silent Junior_HalfRoid_design4_cart_COVID-19_SAVE_ALL_OUT_IGNORE_THE_REST_3qm4ib8m.silent -in:file:silent_struct_type binary -silent_gz -mute all -out:file:silent_struct_type binary -out:file:silent default.out -in:file:boinc_wu_zip Junior_HalfRoid_design4_cart_COVID-19_SAVE_ALL_OUT_IGNORE_THE_REST_3qm4ib8m.zip @Junior_HalfRoid_design4_cart_COVID-19_SAVE_ALL_OUT_IGNORE_THE_REST_3qm4ib8m.flags -nstruct 10000 -cpu_run_time 28800 -watchdog -boinc:max_nstruct 1000 -checkpoint_interval 120 -database minirosetta_database -in::file::zip minirosetta_database.zip -boinc::watchdog -run::rng mt19937 -constant_seed -jran 2285549
Starting watchdog...
Watchdog active.
Starting watchdog...
Watchdog active.
Starting watchdog...
Watchdog active.

ERROR: Assertion `copy_pose.size() == native.size()` failed. MSG:the reference pose must be the same size as the working pose
ERROR:: Exit from: ......srcprotocolsprotein_interface_designfiltersRmsdFilter.cc line: 323
BOINC:: Error reading and gzipping output datafile: default.out
16:20:09 (12496): called boinc_finish(1)

</stderr_txt>
]]>
ID: 95004 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Profile Grant (SSSF)

Send message
Joined: 28 Mar 20
Posts: 977
Credit: 10,608,788
RAC: 23,050
Message 95024 - Posted: 21 Apr 2020, 1:27:40 UTC

Well, this is a new error for me.
041620SR_stapler_stub366_2-6_45_70095258_3mers_0001_0001_SAVE_ALL_OUT_917935_507_1
Don't know if it was the WU or not as the original Task timed out due to missing the deadline (everything that system has downloaded has missed the deadline, nothing has been returned.

       Outcome Computation error
  Client state Compute error
   Exit status -1073741819 (0xC0000005) STATUS_ACCESS_VIOLATION
   Computer ID 4055084
      Run time 18 sec
      CPU time 12 sec
Validate state Invalid



<core_client_version>7.6.22</core_client_version>
<![CDATA[
<message>
(unknown error) - exit code -1073741819 (0xc0000005)
</message>
<stderr_txt>
command: projects/boinc.bakerlab.org_rosetta/rosetta_4.15_windows_x86_64.exe @041620SR_stapler_stub366_2-6_45_70095258_3mers_0001_0001.flags -nstruct 10000 -cpu_run_time 28800 -watchdog -boinc:max_nstruct 1000 -checkpoint_interval 120 -mute all -database minirosetta_database -in::file::zip minirosetta_database.zip -boinc::watchdog -run::rng mt19937 -constant_seed -jran 1331894


Unhandled Exception Detected...

- Unhandled Exception Record -
Reason: Access Violation (0xc0000005) at address 0x0000000000000000 

Engaging BOINC Windows Runtime Debugger...



********************


BOINC Windows Runtime Debugger Version 7.9.0


Dump Timestamp    : 04/21/20 03:35:44
Install Directory : C:Program FilesBOINC
Data Directory    : C:ProgramDataBOINC
Project Symstore  : https://boinc.bakerlab.org/rosetta/symstore
LoadLibraryA( C:ProgramDataBOINCdbghelp.dll ): GetLastError = 126
Loaded Library    : dbghelp.dll
LoadLibraryA( C:ProgramDataBOINCsymsrv.dll ): GetLastError = 126
LoadLibraryA( symsrv.dll ): GetLastError = 126
LoadLibraryA( C:ProgramDataBOINCsrcsrv.dll ): GetLastError = 126
LoadLibraryA( srcsrv.dll ): GetLastError = 126
LoadLibraryA( C:ProgramDataBOINCversion.dll ): GetLastError = 126
Loaded Library    : version.dll
Debugger Engine   : 4.0.5.0
Symbol Search Path: C:ProgramDataBOINCslots11;C:ProgramDataBOINCprojectsboinc.bakerlab.org_rosetta;srv*C:ProgramDataBOINCprojectsboinc.bakerlab.org_rosettasymbols*http://msdl.microsoft.com/download/symbols;srv*C:ProgramDataBOINCprojectsboinc.bakerlab.org_rosettasymbols*https://boinc.bakerlab.org/rosetta/symstore


ModLoad: 00000000a24a0000 00000000057e9000 C:ProgramDataBOINCprojectsboinc.bakerlab.org_rosettarosetta_4.15_windows_x86_64.exe (-exported- Symbols Loaded)
    Linked PDB Filename   : C:cygwin64homeboincRosettamainsourceideVisualStudiox64BoincReleaserosetta_4.13_windows_x86_64.pdb

ModLoad: 00000000c0be0000 00000000001f0000 C:WINDOWSSYSTEM32ntdll.dll (6.2.18362.719) (-exported- Symbols Loaded)
    Linked PDB Filename   : ntdll.pdb
    File Version          : 10.0.18362.329 (WinBuild.160101.0800)
    Company Name          : Microsoft Corporation
    Product Name          : Microsoft&#174; Windows&#174; Operating System
    Product Version       : 10.0.18362.329

ModLoad: 00000000bf5e0000 00000000000b2000 C:WINDOWSSystem32KERNEL32.DLL (6.2.18362.329) (-exported- Symbols Loaded)
    Linked PDB Filename   : kernel32.pdb
    File Version          : 10.0.18362.329 (WinBuild.160101.0800)
    Company Name          : Microsoft Corporation
    Product Name          : Microsoft&#174; Windows&#174; Operating System
    Product Version       : 10.0.18362.329

ModLoad: 00000000bdbd0000 00000000002a3000 C:WINDOWSSystem32KERNELBASE.dll (6.2.18362.719) (-exported- Symbols Loaded)
    Linked PDB Filename   : kernelbase.pdb
    File Version          : 10.0.18362.329 (WinBuild.160101.0800)
    Company Name          : Microsoft Corporation
    Product Name          : Microsoft&#174; Windows&#174; Operating System
    Product Version       : 10.0.18362.329

ModLoad: 00000000c0b30000 000000000006f000 C:WINDOWSSystem32WS2_32.dll (6.2.18362.387) (-exported- Symbols Loaded)
    Linked PDB Filename   : ws2_32.pdb
    File Version          : 10.0.18362.1 (WinBuild.160101.0800)
    Company Name          : Microsoft Corporation
    Product Name          : Microsoft&#174; Windows&#174; Operating System
    Product Version       : 10.0.18362.1

ModLoad: 00000000bf140000 0000000000120000 C:WINDOWSSystem32RPCRT4.dll (6.2.18362.628) (-exported- Symbols Loaded)
    Linked PDB Filename   : rpcrt4.pdb
    File Version          : 10.0.18362.1 (WinBuild.160101.0800)
    Company Name          : Microsoft Corporation
    Product Name          : Microsoft&#174; Windows&#174; Operating System
    Product Version       : 10.0.18362.1

ModLoad: 00000000bf440000 0000000000194000 C:WINDOWSSystem32USER32.dll (6.2.18362.719) (-exported- Symbols Loaded)
    Linked PDB Filename   : user32.pdb
    File Version          : 10.0.17763.802 (WinBuild.160101.0800)
    Company Name          : Microsoft Corporation
    Product Name          : Microsoft&#174; Windows&#174; Operating System
    Product Version       : 10.0.17763.802

ModLoad: 00000000beb60000 0000000000021000 C:WINDOWSSystem32win32u.dll (6.2.18362.719) (-exported- Symbols Loaded)
    Linked PDB Filename   : win32u.pdb
    File Version          : 10.0.18362.719 (WinBuild.160101.0800)
    Company Name          : Microsoft Corporation
    Product Name          : Microsoft&#174; Windows&#174; Operating System
    Product Version       : 10.0.18362.719

ModLoad: 00000000c0880000 0000000000026000 C:WINDOWSSystem32GDI32.dll (6.2.18362.1) (-exported- Symbols Loaded)
    Linked PDB Filename   : gdi32.pdb
    File Version          : 10.0.18362.1 (WinBuild.160101.0800)
    Company Name          : Microsoft Corporation
    Product Name          : Microsoft&#174; Windows&#174; Operating System
    Product Version       : 10.0.18362.1

ModLoad: 00000000be7a0000 0000000000194000 C:WINDOWSSystem32gdi32full.dll (6.2.18362.719) (-exported- Symbols Loaded)
    Linked PDB Filename   : gdi32full.pdb
    File Version          : 10.0.18362.719 (WinBuild.160101.0800)
    Company Name          : Microsoft Corporation
    Product Name          : Microsoft&#174; Windows&#174; Operating System
    Product Version       : 10.0.18362.719

ModLoad: 00000000be600000 000000000009e000 C:WINDOWSSystem32msvcp_win.dll (6.2.18362.387) (-exported- Symbols Loaded)
    Linked PDB Filename   : msvcp_win.pdb
    File Version          : 10.0.18362.387 (WinBuild.160101.0800)
    Company Name          : Microsoft Corporation
    Product Name          : Microsoft&#174; Windows&#174; Operating System
    Product Version       : 10.0.18362.387

ModLoad: 00000000be6a0000 00000000000fa000 C:WINDOWSSystem32ucrtbase.dll (6.2.18362.387) (-exported- Symbols Loaded)
    Linked PDB Filename   : ucrtbase.pdb
    File Version          : 10.0.18362.387 (WinBuild.160101.0800)
    Company Name          : Microsoft Corporation
    Product Name          : Microsoft&#174; Windows&#174; Operating System
    Product Version       : 10.0.18362.387

ModLoad: 00000000c09d0000 00000000000a3000 C:WINDOWSSystem32ADVAPI32.dll (6.2.18362.329) (-exported- Symbols Loaded)
    Linked PDB Filename   : advapi32.pdb
    File Version          : 10.0.18362.1 (WinBuild.160101.0800)
    Company Name          : Microsoft Corporation
    Product Name          : Microsoft&#174; Windows&#174; Operating System
    Product Version       : 10.0.18362.1

ModLoad: 00000000c0a90000 000000000009e000 C:WINDOWSSystem32msvcrt.dll (7.0.18362.1) (-exported- Symbols Loaded)
    Linked PDB Filename   : msvcrt.pdb
    File Version          : 7.0.18362.1 (WinBuild.160101.0800)
    Company Name          : Microsoft Corporation
    Product Name          : Microsoft&#174; Windows&#174; Operating System
    Product Version       : 7.0.18362.1

ModLoad: 00000000bf3a0000 0000000000097000 C:WINDOWSSystem32sechost.dll (6.2.18362.693) (-exported- Symbols Loaded)
    Linked PDB Filename   : sechost.pdb
    File Version          : 10.0.18362.1 (WinBuild.160101.0800)
    Company Name          : Microsoft Corporation
    Product Name          : Microsoft&#174; Windows&#174; Operating System
    Product Version       : 10.0.18362.1

ModLoad: 00000000bfc60000 000000000002e000 C:WINDOWSSystem32IMM32.DLL (6.2.18362.387) (-exported- Symbols Loaded)
    Linked PDB Filename   : imm32.pdb
    File Version          : 10.0.18362.387 (WinBuild.160101.0800)
    Company Name          : Microsoft Corporation
    Product Name          : Microsoft&#174; Windows&#174; Operating System
    Product Version       : 10.0.18362.387

ModLoad: 00000000bdb50000 0000000000011000 C:WINDOWSSystem32kernel.appcore.dll (6.2.18362.1) (-exported- Symbols Loaded)
    Linked PDB Filename   : Kernel.Appcore.pdb
    File Version          : 10.0.18362.1 (WinBuild.160101.0800)
    Company Name          : Microsoft Corporation
    Product Name          : Microsoft&#174; Windows&#174; Operating System
    Product Version       : 10.0.18362.1

ModLoad: 00000000bcb00000 0000000000031000 C:WINDOWSSYSTEM32ntmarta.dll (6.2.18362.1) (-exported- Symbols Loaded)
    Linked PDB Filename   : ntmarta.pdb
    File Version          : 10.0.18362.1 (WinBuild.160101.0800)
    Company Name          : Microsoft Corporation
    Product Name          : Microsoft&#174; Windows&#174; Operating System
    Product Version       : 10.0.18362.1

ModLoad: 00000000a9040000 00000000001f4000 C:WINDOWSSYSTEM32dbghelp.dll (6.2.18362.1) (-exported- Symbols Loaded)
    Linked PDB Filename   : dbghelp.pdb
    File Version          : 10.0.18362.1 (WinBuild.160101.0800)
    Company Name          : Microsoft Corporation
    Product Name          : Microsoft&#174; Windows&#174; Operating System
    Product Version       : 10.0.18362.1

ModLoad: 00000000bebc0000 0000000000080000 C:WINDOWSSystem32bcryptPrimitives.dll (6.2.18362.295) (-exported- Symbols Loaded)
    Linked PDB Filename   : bcryptprimitives.pdb
    File Version          : 10.0.18362.295 (WinBuild.160101.0800)
    Company Name          : Microsoft Corporation
    Product Name          : Microsoft&#174; Windows&#174; Operating System
    Product Version       : 10.0.18362.295

ModLoad: 00000000b7ec0000 000000000000a000 C:WINDOWSSYSTEM32version.dll (6.2.18362.1) (-exported- Symbols Loaded)
    Linked PDB Filename   : version.pdb
    File Version          : 10.0.18362.1 (WinBuild.160101.0800)
    Company Name          : Microsoft Corporation
    Product Name          : Microsoft&#174; Windows&#174; Operating System
    Product Version       : 10.0.18362.1



*** Dump of the Process Statistics: ***

- I/O Operations Counters -
Read: 66964, Write: 20634, Other 272401

- I/O Transfers Counters -
Read: 522084341, Write: 1006837730, Other 373586

- Paged Pool Usage -
QuotaPagedPoolUsage: 317400, QuotaPeakPagedPoolUsage: 317528
QuotaNonPagedPoolUsage: 6792, QuotaPeakNonPagedPoolUsage: 7352

- Virtual Memory Usage -
VirtualSize: 83050496, PeakVirtualSize: 895631360

- Pagefile Usage -
PagefileUsage: 83050496, PeakPagefileUsage: 83050496

- Working Set Size -
WorkingSetSize: 103501824, PeakWorkingSetSize: 103505920, PageFaultCount: 26098

*** Dump of thread ID 824 (state: Initialized): ***

- Information -
Status: Base Priority: Normal, Priority: Normal, , Kernel Time: 0.000000, User Time: 0.000000, Wait Time: 0.000000

- Unhandled Exception Record -
Reason: Access Violation (0xc0000005) at address 0x0000000000000000 

- Registers -
rax=000000000000003a rbx=000000009a954780 rcx=000000009b359db0 rdx=000000009b439ee8 rsi=000000000000000b rdi=000000009b359db0
r8=000000000000003a r9=0000000000000421 r10=00000000a6463328 r11=0000000030b5a300 r12=00000000a24a0000 r13=0000000030b5fb90
r14=0000000030b5aa40 r15=0000000000487b05 rip=0000000000000000 rsp=0000000030b5a378 rbp=0000000000000000
cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206

- Callstack -
ChildEBP RetAddr  Args to Child
(-nosymbols- PC == 0)
30b5a370 a430f55c 00000000 a6463208 a6463328 a6027548 !&#128;+0x0 
30b5a3a0 a2935bd5 9a954780 30b5a440 30b5abc0 a291fe6d rosetta_4.15_windows_x86_64!xmlInitializeDict+0x0 
30b5a3d0 a5aa3e4e a6989c38 30b5fb90 00000000 a291fb75 rosetta_4.15_windows_x86_64!cppdb::mutex::mutex+0x0 
30b5a400 a29202f0 30b5b0b0 28d1e4a7 30b5aa08 30b5aa90 rosetta_4.15_windows_x86_64!xmlCheckHTTPInput+0x0 
30b5a470 c0c8121f 00000000 30b5a9f0 30b5b0b0 30b5b0b0 rosetta_4.15_windows_x86_64!cppdb::backend::driver::connect+0x0 
30b5a4a0 c0c4a289 00000001 a24a0000 00000000 a7a3405c ntdll!__chkstk+0x0 
30b5abb0 c0c7fe8e 00000020 00000000 a6101208 00000003 ntdll!RtlRaiseException+0x0 
30b5b360 a2ba86cb fffffffe 9ede19b8 ffffffff a2bb61a5 ntdll!KiUserExceptionDispatcher+0x0 
30b5b3b0 a2bb7f70 a6101158 9ede1710 a6101158 30b5b4a9 rosetta_4.15_windows_x86_64!cppdb::mutex::mutex+0x0 
30b5b4e0 a2cce1b8 9e6056c8 9ef54830 9ede1710 9ef54830 rosetta_4.15_windows_x86_64!cppdb::mutex::mutex+0x0 
30b5c090 a2c68dbc 9f049310 c0c1ba17 9a8d0000 00000000 rosetta_4.15_windows_x86_64!cppdb::backend::statement::cache+0x0 
30b5c290 a2c68ade 30b5c378 00000000 30b5c560 00000000 rosetta_4.15_windows_x86_64!cppdb::backend::statement::cache+0x0 
30b5c3f0 a2bc8631 30b5c568 00000000 9a9542d0 30b5c630 rosetta_4.15_windows_x86_64!cppdb::backend::statement::cache+0x0 
30b5c7b0 a2bce5e8 30b5cb00 30b5cb00 30b5cb00 00000000 rosetta_4.15_windows_x86_64!cppdb::backend::statement::cache+0x0 
30b5ce00 a2bccbbb 9b039580 30b5ce60 9af0cf30 9af0cf30 rosetta_4.15_windows_x86_64!cppdb::backend::statement::cache+0x0 
30b5cf60 a2b36927 00000000 30b5d070 9af0cf30 30b5d270 rosetta_4.15_windows_x86_64!cppdb::backend::statement::cache+0x0 
30b5d0d0 a2b39fa6 a6023ae0 a2914f90 9af02dc0 9af02dc0 rosetta_4.15_windows_x86_64!cppdb::mutex::mutex+0x0 
30b5d140 a2b39ecc 30b5d448 30b5d2b9 30b5d448 9af0cf30 rosetta_4.15_windows_x86_64!cppdb::mutex::mutex+0x0 
30b5d1f0 a2bffd65 30b5d448 00000000 9a9547a0 30b5d920 rosetta_4.15_windows_x86_64!cppdb::mutex::mutex+0x0 
30b5d310 a2bfee52 00000000 30b5d448 30b5d5f0 00000000 rosetta_4.15_windows_x86_64!cppdb::backend::statement::cache+0x0 
30b5d3e0 a2bff592 00000030 30b5d5f0 00000001 00000000 rosetta_4.15_windows_x86_64!cppdb::backend::statement::cache+0x0 
30b5d550 a305a603 30b5d5f0 30b5dcd0 ffffffff a2920773 rosetta_4.15_windows_x86_64!cppdb::backend::statement::cache+0x0 
30b5d840 a305d169 00000000 30b5d920 00000000 30b5dcd0 rosetta_4.15_windows_x86_64!cppdb::backend::statement::cache+0x0 
30b5dbd0 a305637a 30b5dc10 30b5dcd0 9e141490 9ae558d0 rosetta_4.15_windows_x86_64!cppdb::backend::statement::cache+0x0 
30b5dc30 a3270ba0 30b5dcd0 30b5e3f8 9af02dc0 00000000 rosetta_4.15_windows_x86_64!cppdb::backend::statement::cache+0x0 
30b5e3c0 a3270614 9efd5680 9ef4e1d0 a78dd060 a2916bd6 rosetta_4.15_windows_x86_64!cppdb::backend::statement::cache+0x0 
30b5e420 a3279f6e 30b5e510 9efd53b0 30b5e530 30b5ec80 rosetta_4.15_windows_x86_64!cppdb::backend::statement::cache+0x0 
30b5eba0 a3279604 da51227c da51234c a7847740 a329abc4 rosetta_4.15_windows_x86_64!cppdb::backend::statement::cache+0x0 
30b5ec30 a32796be 00000005 30b5f048 9ae558d0 00000001 rosetta_4.15_windows_x86_64!cppdb::backend::statement::cache+0x0 
30b5edd0 a291d192 9b0eb160 9b0eb160 9ae558d0 9add5550 rosetta_4.15_windows_x86_64!cppdb::backend::statement::cache+0x0 
30b5fb80 a2927b05 00000000 00000000 a7846c58 00000000 rosetta_4.15_windows_x86_64!cppdb::backend::driver::connect+0x0 
30b5fbc0 bf5f7bd4 00000000 00000000 00000000 00000000 rosetta_4.15_windows_x86_64!cppdb::backend::driver::connect+0x0 
30b5fbf0 c0c4ced1 00000000 00000000 00000000 00000000 KERNEL32!BaseThreadInitThunk+0x0 
30b5fc70 00000000 00000000 00000000 00000000 00000000 ntdll!RtlUserThreadStart+0x0 

*** Dump of thread ID 32762 (state: Initialized): ***

- Information -
Status: Base Priority: Normal, Priority: Unknown, , Kernel Time: 6.000000, User Time: 0.000000, Wait Time: 1179383296.000000

- Registers -
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
r8=0000000000000000 r9=0000000000000000 r10=0000000000000000 r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000 rip=0000000000000000 rsp=0000000000000000 rbp=0000000000000000
cs=0000  ss=0000  ds=0000  es=0000  fs=0000  gs=0000             efl=00000000

- Callstack -
ChildEBP RetAddr  Args to Child
(-nosymbols- PC == 0)
00000000 00000000 00000000 00000000 00000000 00000000 !+0x0 

*** Dump of thread ID 30807870 (state: Unknown): ***

- Information -
Status: Base Priority: Normal, Priority: Unknown, , Kernel Time: 17179869184.000000, User Time: 21474836480.000000, Wait Time: 0.000000

- Registers -
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
r8=0000000000000000 r9=0000000000000000 r10=0000000000000000 r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000 rip=0000000000000000 rsp=0000000000000000 rbp=0000000000000000
cs=0000  ss=0000  ds=0000  es=0000  fs=0000  gs=0000             efl=00000000

- Callstack -
ChildEBP RetAddr  Args to Child
(-nosymbols- PC == 0)
00000000 00000000 00000000 00000000 00000000 00000000 !+0x0 


*** Debug Message Dump ****


*** Foreground Window Data ***
    Window Name      : 
    Window Class     : 
    Window Process ID: 0
    Window Thread ID : 0

Exiting...

</stderr_txt>
]]>

Grant
Darwin NT
ID: 95024 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Tomcat雄猫

Send message
Joined: 20 Dec 14
Posts: 136
Credit: 3,592,999
RAC: 3,970
Message 95034 - Posted: 21 Apr 2020, 7:56:20 UTC - in response to Message 93363.  

I found the "suspend when other processes use the CPU" to be not operable on OS X.


This issues appears to have been fixed in the latest BOINC MAC release, at least for MacOS Catalina,
ID: 95034 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Profile [VENETO] boboviz

Send message
Joined: 1 Dec 05
Posts: 1392
Credit: 5,784,791
RAC: 5,155
Message 95072 - Posted: 21 Apr 2020, 21:27:44 UTC

Is not the first..
1156578590
ERROR: Assertion `copy_pose.size() == native.size()` failed. MSG:the reference pose must be the same size as the working pose
ERROR:: Exit from: ......srcprotocolsprotein_interface_designfiltersRmsdFilter.cc line: 323
BOINC:: Error reading and gzipping output datafile: default.out
22:55:42 (10128): called boinc_finish(1)

ID: 95072 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Previous · 1 . . . 7 · 8 · 9 · 10 · 11 · 12 · 13 . . . 31 · Next

Message boards : Number crunching : Rosetta 4.1+ and 4.2+



©2021 University of Washington
https://www.bakerlab.org