There is a thread in the SETI number crunching forums about missing 'Deny Request' button on the team change founder transfer page. Question on Team Ownership Transfer.

I created a new test group, and two test members. I then put in a founder transfer request. An email was received by the founder. Checking the 'team change founder transfer page', I found the 'Deny Transfer' button.

Finally I removed the member that requested the founder transfer from the team. When I checked the 'team change founder transfer page', I found the 'Deny Transfer' button had been removed. But there was no email sent to the founder saying that the requester had left the team and the transfer was not longer valid.

The missing 'deny transfer' button seems to be causing a problem. Could an email be sent to the founder, if the person requesting a founder transfer decides to leave the team, stating that the request is no longer valid.

---

Thanks for finding the cause of this, I'll check in a fix soon.

---

Fix checked into SVN.

---

Fix checked into SVN.

We have the same problem for SETI.Germany. Someone called Timo has requested the team founder change, our admin only gets this answers:

Team member Timo requested this team's foundership on 7 Nov 2007, but left the team, thus canceling the request. To assign foundership of this team to another member, check the box next to member name and click Change founder below.

Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 49 bytes) in /disks/setifiler1/home/boincadm/projects/sah/html/inc/db_conn.inc on line 64

In my account the "initiate transfer" has changed to "deferred", I've tried a founder transfer request nevertheless for testing (after this mail) and get this answer:

Founder change has already been requested by Timo on 7 Nov 2007.

I think something fishy is still happening, Timo is still on the Team if I believe his account page, how comes the mail said he's no longer on the team?

BTW: I think the "initiate transfer" button is far too prominent and easy to click, why should it be on every team stats page at all? If someone want's a transfer, s/he can go a bit longer ways to reach this goal, and people who just clicked there to look what it's good for won't bother the founders.

---

Gruesse vom Saenger

For questions about Boinc look in the BOINC-Wiki

Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 49 bytes) in /disks/setifiler1/home/boincadm/projects/sah/html/inc/db_conn.inc on line 64

Over 67MB? That's one hell of a memory leak.

---

...
Over 67MB? That's one hell of a memory leak.

Not a memory leak, just a limit to protect the web server.

It starts to build a HTML table over all members of that team.

Here you can see why that happens : Members 19726

The DB query is not limited to "next 20" or so as on the stats pages.
I guess, restricting the query to the required attributes instead of "*" would help too.

@Saenger : Can you even list the email addresses or the team history of all members? Imo. that should give you the same error.

...
Over 67MB? That's one hell of a memory leak.

Not a memory leak, just a limit to protect the web server.

The limit is 67MB to protect the webserver. I consider it a memory leak in the PHP script if it managed to reach such a limit.

---

... I consider it a memory leak in the PHP script if it managed to reach such a limit.

Question of definition ;-) For me a leak is memory that a process allocates without ever releasing it, when it isn't needed anymore. The allocation in this case is by design, underestimated requirements.

p.s.: the retrieved amount of data in such a query is larger than the user DB export for the stats, as the latter contains just a subset of attributes.

Question of definition ;-) For me a leak is memory that a process allocates without ever releasing it, when it isn't needed anymore. The allocation in this case is by design, underestimated requirements.

Maybe if the limit wasn't there, it would allocate an infinite amount of memory (=bug).

---

... Maybe if the limit wasn't there, it would allocate an infinite amount of memory (=bug).

You're right - but I think, that such a DB query on smaller teams would not hit that limit yet or we would already have heard a lot more complaints.

That's why I asked Saenger to check email list and team history. If those produce the same error, it is the query result size that causes it. Afterall it tries to keep the complete result in memory in order to allow PHP to process it with "forall()"

Note to the one who will start to fix it ... fixing the memory requirements on server side alone might not be sufficient, web browsers tend to panic when a HTML table reaches a certain size (# of table rows).

So maybe a solution like a loop that splits the query into several "limit 50" query chunks with an extra HTML table arround each block of 50 entries would be a good thing.

@Saenger : Can you even list the email addresses or the team history of all members? Imo. that should give you the same error.

I've got to ask our admins, I'm neither admin nor founder @Seti (only on 23 other;).

---

Gruesse vom Saenger

For questions about Boinc look in the BOINC-Wiki

@Saenger : Can you even list the email addresses or the team history of all members? Imo. that should give you the same error.

I've got to ask our admins, I'm neither admin nor founder @Seti (only on 23 other;).

Sorry, can't edit any more, here's the answer:

E-Mail Adressen der Mitglieder bei welchem Projekt ?

Wenn du Seti meinst, da erscheint dieser Fehler:


Zitat:

Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 33 bytes) in /disks/setifiler1/home/boincadm/projects/sah/html/inc/db_conn.inc on line 61

__________________

---

Gruesse vom Saenger

For questions about Boinc look in the BOINC-Wiki

[@Saenger : Can you even list the email addresses or the team history of all members? Imo. that should give you the same error.

Hi Ananas,

to quickly answer your Question: I cannot list the Email adresses of our Team nor can i list the Team History. I get the Error mentioned above all the Time.

cheers
aendgraend

---

... I cannot list the Email adresses of our Team nor can i list the Team History. I get the Error mentioned above all the Time. ...

That's a clear sign for exhausted PHP memory during the SQL query that would have all attributes of all members of SETI.Germany as a result.

This can only be fixed by either

- splitting the query into smaller chunks (i.e. request "only" 1000 records each time with the "< last 1000 ... next 1000 >" stuff (more work but a permanent solution) or

- selecting only the attributes, that this query needs (which will lead to the same problem again when the team grows much larger)

Increasing the allowed PHP memory is not a good solution because that can sooner or later lead to server problems.


p.s.: "select *" for each and every query produces a high server IO and memory load anyway so maybe both modifications should be implemented.