babynus post=36086 wrote: About your traces, just add insformation to check if it is an infinite look, of just "long" execution.
For instance instead of writing
debugLog("PlannedWork::reverse");
try something like debugLog("PlannedWork::reverse($nodeId,$idProject)");
This output was created from a
very full backtrace, so I have the full parameters in an 1.1 MB file.
You can retrieve it from here
. It's a huge JSON plus a rude php code to print whatever you want to see from that mess, but it does contain the whole backtrace.
So trace will be more explict : always the same or changing.
Possibly it is just long execution on large project on not too powerfull server
The project contains about 15 tasks, and a handful of everything, like a good test should.
The machine is, well, it is a container running on plenty of resources, but it's obviosuly looping since normal recalculation took about 500 ms and now it takes 5 minutes, about 50 times the memory and then crash, so I am fairly sure it's not the machine.
(Sidenote: I found Projeqtor a few weeks ago by accident, and I am still in awe how versatile and smart it is. I think I have tested most of the available project management code on Linux, and while your UI is not always the best, the code, feature-wise, is not even in the same universe as the others. I still try to get to know the various logic in Projeqtor, and I apologise in advance for my questions yet to come.
)