Closed
Bug 683388
Opened 14 years ago
Closed 12 years ago
[stage] When loading correlation reports - Fatal error: Allowed memory size of 402653184 bytes exhausted
Categories
(Socorro :: General, task)
Socorro
General
Tracking
(Not tracked)
RESOLVED
WONTFIX
Future
People
(Reporter: mbrandt, Assigned: rhelmer)
References
()
Details
Attachments
(1 file)
|
193.92 KB,
image/png
|
Details |
Loading correlation reports on stage results in a memory error. Talking to rhelmer on the channel it sounds like this was fixed on production.
This appears to be a duplicate of:
https://bugzilla.mozilla.org/show_bug.cgi?id=641932#c2
bug 567869
"Fatal error: Allowed memory size of 402653184 bytes exhausted (tried to allocate 4097 bytes) in /data/socorro/htdocs/application/libraries/Correlation.php on line 117"
1. goto the correlations tab for https://crash-stats.allizom.org/report/list?range_value=7&range_unit=days&date=2011-08-24&signature=hang%20%7C%20mozilla%3A%3Aplugins%3A%3APPluginInstanceParent%3A%3ACallNPP_HandleEvent%28mozilla%3A%3Aplugins%3A%3ANPRemoteEvent%20const%26%2C%20short%2A%29&version=Firefox%3A6.0b5
2. load the modules by version
Actual:
Fatal error: Allowed memory size of 402653184 bytes exhausted (tried to allocate 4097 bytes) in /data/socorro/htdocs/application/libraries/Correlation.php on line 117
Expected:
Either the correlation loads, or there's an appropriate error message, rather than this allocation failure.
Comment 1•14 years ago
|
||
Shouldn't be an issue on prod; if it is we can bump the config. This should be solved properly by bug 650904, too.
Target Milestone: 2.2.2 → 2.2.3
Comment 2•14 years ago
|
||
FWIW, I have seen this on prod as well, but haven't reported it so far - and we should really redo correlation reports in a more Socorro-ish way anyhow...
Comment 3•14 years ago
|
||
https://crash-stats.mozilla.com/report/list?range_value=7&range_unit=days&date=2011-09-06&signature=PInvokeCalliWorker&version=Firefox%3A6.0.1 gets that when trying to load modules by versions.
Updated•14 years ago
|
Assignee: nobody → chris.lonnen
Updated•14 years ago
|
Target Milestone: 2.2.4 → 2.3
| Assignee | ||
Updated•14 years ago
|
Target Milestone: 2.3 → 2.3.1
| Assignee | ||
Updated•14 years ago
|
Target Milestone: 2.3.1 → 2.3.2
Updated•14 years ago
|
Target Milestone: 2.4 → 2.4.2
Updated•14 years ago
|
Component: Socorro → General
Product: Webtools → Socorro
Comment 5•13 years ago
|
||
mass migration of correlation-report related bugs that won't land today.
Target Milestone: 2.4.2 → 2.4.3
Updated•13 years ago
|
Target Milestone: 2.4.3 → 2.4.4
Updated•13 years ago
|
Target Milestone: 2.4.4 → 2.5.1
Updated•13 years ago
|
Target Milestone: 2.5.1 → 2.5.2
Comment 6•13 years ago
|
||
Kicking these out to 2.6, which roughly matches the next week I'll be working on Socorro. If someone wants to poach these to get them done earlier, that's fine with me.
Target Milestone: 2.5.2 → 2.6
Updated•13 years ago
|
Target Milestone: 4 → 6
Updated•13 years ago
|
Target Milestone: 6 → 8
Comment 7•13 years ago
|
||
Should be fixed by the other correlation bugs
Assignee: chris.lonnen → peterbe
Updated•13 years ago
|
Target Milestone: 8 → 10
Updated•13 years ago
|
Target Milestone: 10 → 11
Updated•13 years ago
|
Target Milestone: 11 → Future
Updated•13 years ago
|
Assignee: peterbe → rhelmer
| Assignee | ||
Comment 8•12 years ago
|
||
Moved to django instead :)
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•