Closed
Bug 461215
Opened 17 years ago
Closed 17 years ago
Dev CP fails to load for authors with many add-ons
Categories
(addons.mozilla.org Graveyard :: Developer Pages, defect)
addons.mozilla.org Graveyard
Developer Pages
Tracking
(Not tracked)
RESOLVED
FIXED
4.0.3
People
(Reporter: wenzel, Assigned: fligtar)
Details
Attachments
(1 file)
|
2.07 KB,
patch
|
wenzel
:
review+
|
Details | Diff | Splinter Review |
The user with ID 37347 can't access the Dev CP (when he clicks on the link, the browser waits, then brings up a white page).
I found out he is listed as the author of 16 add-ons. A quick look at the source code for the index action of the developer controller shows that it pulls in a lot of data:
1341 //Bind necessary models
1342 $this->User->bindFully();
1343 $this->Addontype->bindFully();
1344 $this->Version->bindFully();
1345 $this->Addon->bindFully();
My guess is we're hitting the memory limit here, which goes quite easy with the numerous associations these models have.
| Reporter | ||
Comment 1•17 years ago
|
||
morgamic writes:
"I recommend:
* Only fully binding Addons
* Doing a manual query to pull addon_ids prior to the Addons query"
Comment 2•17 years ago
|
||
I've had 25 add-ons in my Dev CP for a long time with minimal delay. 23 are search engines though so maybe they are pulling less data.
| Reporter | ||
Comment 3•17 years ago
|
||
I will try to reproduce the error locally and I am just importing a fresh DB dump for that purpose (which, obviously, takes a long time). I should hopefully be able to get an error message off the logs then.
| Reporter | ||
Comment 4•17 years ago
|
||
It's also possible that these add-ons have a lot of versions and files or something -- keep in mind, *all* associations are pulled here.
| Assignee | ||
Comment 5•17 years ago
|
||
It is weird that we're getting these complaints all of the sudden. I'm not sure it's connected with how many add-ons an author has. One of the emails amo-editors got yesterday said that someone just created an account and then created an add-on and couldn't access the Dev Tools index after that.
Comment 6•17 years ago
|
||
Logging in as user id 37347 on my staging copy says it's an execution time issue. Bumping the time from 30 -> 60 fixes it. comment #1 is a good move.
| Assignee | ||
Comment 7•17 years ago
|
||
I will have time to look at this tomorrow, but have a big project I'm working on tonight... based on the number of reports of this on IRC and email, we may need to fix and push it ASAP.
| Assignee | ||
Updated•17 years ago
|
Assignee: nobody → fligtar
Severity: major → critical
Target Milestone: --- → 4.0.3
| Assignee | ||
Comment 8•17 years ago
|
||
Copied some code from the new dev cp index (dashboard()) and morphed it a bit to format the array the same way the old stuff did.
This fixes the execution time problems for me.
Attachment #345010 -
Flags: review?(fwenzel)
| Reporter | ||
Comment 9•17 years ago
|
||
Comment on attachment 345010 [details] [diff] [review]
patch, v1
That solves it for me as well. I tried the user account from comment 0.
Attachment #345010 -
Flags: review?(fwenzel) → review+
| Assignee | ||
Comment 10•17 years ago
|
||
r19378.
Is there a push scheduled for this week? If not, I think this is important enough to push ASAP. I personally have seen about 15-20 complaints from people experiencing this, and probably many more who haven't reported it or assume it's a problem on their end.
Updated•17 years ago
|
Keywords: push-needed
Jason, is this now working for you?
Updated•9 years ago
|
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•