Milkyway's Astronomy_1.07 does not like it when the BOINC service is stopped.

I just quit the service under Windows 2000 to go play some C&C Red Alert: Yuri's revenge. Normally this isn't a problem, applications running at that time stop and don't mind. Apparently Astronomy_1.07 does mind my gaming habits. Up pops a warning message that Astronomy_1.07 has generated errors and will need to be closed, an error report is made.

Checking stderr.txt in the slot it says:

c:\research\boinc_samples\astronomy\star_points.c(87) : {397186} normal block at 0x01960FD8, 24 bytes long.
 Data: <[ S  ,J@fASSERT: output.c(1688) : Assertion failed: ("'n' format specifier disabled", 0)

Unhandled Exception Detected...

- Unhandled Exception Record -
Reason: Breakpoint Encountered (0x80000003) at address 0x0047F646

Engaging BOINC Windows Runtime Debugger...

Well thanks. :-) I will assume that the task that I still had is crashed.

BOINC 5.10.30

---

Jord.

The BOINC FAQ Service.

Milkyway's Astronomy_1.07 does not like it when the BOINC service is stopped.

I just quit the service under Windows 2000 to go play some C&C Red Alert: Yuri's revenge. Normally this isn't a problem, applications running at that time stop and don't mind. Apparently Astronomy_1.07 does mind my gaming habits. Up pops a warning message that Astronomy_1.07 has generated errors and will need to be closed, an error report is made.

I get these pop-ups all the time with this project. And I do not stop BOINC for gaming (or anything else for that matter). I also do not run it as a service. So whatever the problem(s) is, it goes beyond just stopping the service.

Errors happen, and are expected from time to time. However, these pop-up errors are a real problem, because they impact other projects as well. Because the pops-ups do not release the thread/core until they are manually dismissed. And that means the thread/core sits idle until we happen to notice it, so not only is this project sitting idle on that thread/core, but it also means that none of the other projects can run either.

---

I get these pop-ups all the time with this project. And I do not stop BOINC for gaming (or anything else for that matter). I also do not run it as a service. So whatever the problem(s) is, it goes beyond just stopping the service.

Errors happen, and are expected from time to time. However, these pop-up errors are a real problem, because they impact other projects as well. Because the pops-ups do not release the thread/core until they are manually dismissed. And that means the thread/core sits idle until we happen to notice it, so not only is this project sitting idle on that thread/core, but it also means that none of the other projects can run either.

I had the same Problem on one of my Computers.
resultid=119879
resultid=119878

This results started at the same time on my computer and stopped after an CPU time of 26.9 sec with an Popup window on my Screen. Boinc can't change to an other Project till i close the Popup window.

Matthias

Have been getting this pop up too.

Usually happens if I have to suspend BOINC for a moment.

Other times it just happens out of the blue for no apparent reason.

Is anyone else seeing their BOINC client going into a not responding mode for a few seconds now and then? Seems to do this a lot now and it started about the same time that I attached to Milkyway.

It seems like the easiest way to break the workunits is to put BOINC on Snooze while a Milkyway WU is running. I get an error every time.

Hi,

I get these pop-ups all the time with this project....

....However, these pop-up errors are a real problem, because they impact other projects as well. Because the pops-ups do not release the thread/core until they are manually dismissed....

Hmm, not on my host they don't....

I've had my fair share of these pop-ups and *NOT ONCE* has BOINC failed to switch to the next task and continue on normally! In fact, the first time I saw these pop-ups I had 6 of them on the screen simultaneously....and BOINC was happily crunching away at Einstein....

Setup here is WinXP x64 and BOINC v5.10.13 64bit build (and I run BOINC the proper way - as a service! :-)).


TTFN - Pete.

---

Hi,

I get these pop-ups all the time with this project....

....However, these pop-up errors are a real problem, because they impact other projects as well. Because the pops-ups do not release the thread/core until they are manually dismissed....

Hmm, not on my host they don't....

I've had my fair share of these pop-ups and *NOT ONCE* has BOINC failed to switch to the next task and continue on normally! In fact, the first time I saw these pop-ups I had 6 of them on the screen simultaneously....and BOINC was happily crunching away at Einstein....

Setup here is WinXP x64 and BOINC v5.10.13 64bit build (and I run BOINC the proper way - as a service! :-)).


TTFN - Pete.

It does look like we're having some problems with the windows application. We're taking a look into it to see what the problem is. I've gotten these as well on my old windows box so i hope that we can figure out whats going wrong soon. We should be rolling out an update to the application, so this should fix things.

It seems like the easiest way to break the workunits is to put BOINC on Snooze while a Milkyway WU is running. I get an error every time.

I can confirm that here too.

---

me@rescam.org

It seems like the easiest way to break the workunits is to put BOINC on Snooze while a Milkyway WU is running. I get an error every time.

I can confirm that here too.

I'll see if i can replicate that. There might be some problem with checkpointing.

It seems like the easiest way to break the workunits is to put BOINC on Snooze while a Milkyway WU is running. I get an error every time.

I can confirm that here too.

I'll see if i can replicate that. There might be some problem with checkpointing.

Thanks Travis!