Missing object files
 

For all those who need/want to compile on Linux - attached missing object files.

v25.6.2 [Win64] seems to have (partially) broken [i]LowMemWhileRunning[/i]. It only notices some of the running programs, not all of them. I tried v25.6.1 again to make sure and that worked fine.[quote]LowMemWhileRunning=[b]photoshop[/b],[b]ptgui[/b],bsplayer.exe,googleearth.exe,StaxRip[/quote](bold is broken, works as expected). The only common issue I see is that both undetected programs begin with "P". Are you maybe enumerating running processes and then handling ones starting with "P" (like "Prime95") in some special way that no longer includes LowMemWhileRunning check?

[QUOTE=James Heinrich;252251]v25.6.2 [Win64] seems to have (partially) broken [i]LowMemWhileRunning[/i]. [/QUOTE]

Odd. That code hasn't changed in ages.

[QUOTE=Prime95;252264]Odd. That code hasn't changed in ages.[/QUOTE]Maybe the code pixies have been flipping bits when you weren't looking :smile:
Works perfectly fine in v25.6.1, works imperfectly in v25.6.2
Let me know if you want me to test anything related to this.

I'm not sure if it's related, but I see a bunch of "Memory allocation error. Trying again using less memory" messages overnight in results.txt, from running v25.6.2. I never had that problem with v25.6.1

It could be some sort of software regression.

From running 25.11,, I upgraded to 26.5 on my AMD Phenom II six core beast running xubuntu 10.10.

25.11 is in a directory called ~/prime95 and running happily (except that ./mprime -dm doesn't seem to work properly; I get status but not a menu)( about 25% into 3 separate LL tests) 26.5 is in ~/Downloads/prime95_26_5.

When I run 26.5 from the 25.11 directory, without specifying a working directory, it uses the directory of the mprime image instead of the current working directlory; thus I have a bit of cleanup to do; I've been too sick this weekend to do much.
that is
~/prime95:../Downloads/prime95_26_5/mprime -md
finds the six cores no problem, but it doesn't find the existing worktodo.txt in ~/prime95.

Not sure if this is a bug, but I do find the behavior counterintuitive.

Issue with SOB P-1 factoring using 26.5 build 1.

Last night I pick up a new wu for SOB using 26.5. It ran P-1 and completed with this residue. [Sat Feb 12 23:42:47 2011]
UID: engracio, 55459*2^19307926+1 completed P-1, B1=55000, B2=440000, We1: F3AE675D, AID: 00000000000000000000000000100CF8

I checked my worktodo file and it had this.
[Worker #2]
PRP=00000000000000000000000000100CF8,55459,2,19307926,1,56,2.1
PRP=00000000000000000000000000100BDB,21181,2,19471412,1

It completed 6% overnight. This morning when the computer rebooted, the client started to run P-1 again. I let it run/complete and got this residue.
[Sun Feb 13 14:07:54 2011]
UID: engracio, 55459*2^19307926+1 completed P-1, B1=55000, B2=440000, We1: F3AE675D, AID: 00000000000000000000000000100CF8

Again it still had the 56,2.1 on the worktodo file.
PRP=00000000000000000000000000100CF8,55459,2,19307926,1,56,2.1

When I restarted the client just poking around, P-1 started again.

[Feb 13 14:01] 55459*2^19307926+1 stage 2 is 72.94% complete. Time: 481.353 sec.
[Feb 13 14:07] 55459*2^19307926+1 stage 2 complete. 54462 transforms. Time: 1429.160 sec.
[Feb 13 14:07] Starting stage 2 GCD - please be patient.
[Feb 13 14:07] Stage 2 GCD complete. Time: 37.997 sec.
[Feb 13 14:07] 55459*2^19307926+1 completed P-1, B1=55000, B2=440000, We1: F3AE675D
[Feb 13 14:07] Setting affinity to run helper thread 1 on any logical CPU.
[Feb 13 14:07] Resuming PRP test of 55459*2^19307926+1 using all-complex AMD K10 type-3 FFT length 1728K, Pass1=384, Pass2=4608, 2 threads
[Feb 13 14:07] Iteration: 1236008 / 19307941 [6.40%].
[Feb 13 14:09] Iteration: 1240000 / 19307941 [6.42%]. Per iteration time: 0.024 sec.
[Feb 13 14:10] Stopping PRP test of 55459*2^19307926+1 at iteration 1243193 [6.43%]
[Feb 13 14:10] Worker stopped.
[Feb 13 14:11] Waiting 5 seconds to stagger worker starts.
[Feb 13 14:11] Worker starting
[Feb 13 14:11] Setting affinity to run worker on any logical CPU.
[Feb 13 14:11] Optimal P-1 factoring of 55459*2^19307926+1 using up to 1536MB of memory.
[Feb 13 14:11] Assuming no factors below 2^56 and 2.1 primality tests saved if a factor is found.
[Feb 13 14:11] Optimal bounds are B1=55000, B2=440000
[Feb 13 14:11] Chance of finding a factor is an estimated 0.349%
[Feb 13 14:11] Using all-complex AMD K10 type-3 FFT length 1728K, Pass1=384, Pass2=4608, 2 threads
[Feb 13 14:11] Setting affinity to run helper thread 1 on any logical CPU.
[Feb 13 14:15] 55459*2^19307926+1 stage 1 is 12.61% complete. Time: 246.959 sec.
[Feb 13 14:15] Worker stopped.

An Mxxxxx_xxxxxx residue is also on the work folder. I moved the wu below until ideas are suggested. Any ideas?

[QUOTE=engracio;252383]Issue with SOB P-1 factoring using 26.5 build 1. Any ideas?[/QUOTE]

This is a side effect of a bug fix in 26.4. I've coded up a fix for 26.5 build 3.

[QUOTE=Prime95;252396]This is a side effect of a bug fix in 26.4. I've coded up a fix for 26.5 build 3.[/QUOTE]

Thanks George, I was able to reproduce the issue on a different computer except I ran 26.4 first with no issue, then 26.5 where 56,2.1 was added and not removed after completion of P-1. The wu did not restart P-1 when I manually deleted 26,2.1 add on.:smile:

gwnum v26.5 in PFGW gives 885176830*3^5-1 as PRP, when it can be factored as 101207*2125327. There are a couple more if you care, but I suspect that a small change in gwnum could fix all three of them.