[Wikidata-bugs] [Maniphest] [Commented On] T249018: A revision of https://wikidata.beta.wmflabs.org/wiki/Q64 consistently doesn't load on beta wikidata

2020-05-04 Thread RhinosF1
RhinosF1 added a comment. I know what I did. Sorry, still half alseep. > If you report this error to the Wikimedia System Administrators, please include the details below. > PHP fatal error: > Allowed memory size of 692060160 bytes exhausted (tried to allocate 1179648

[Wikidata-bugs] [Maniphest] [Commented On] T249018: A revision of https://wikidata.beta.wmflabs.org/wiki/Q64 consistently doesn't load on beta wikidata

2020-05-04 Thread DannyS712
DannyS712 added a comment. In T249018#6103373 , @RhinosF1 wrote: > @DannyS712: loads fine here tried again and got `Allowed memory size of 692060160 bytes exhausted (tried to allocate 4194304 bytes)` TASK DETAIL

[Wikidata-bugs] [Maniphest] [Commented On] T249018: A revision of https://wikidata.beta.wmflabs.org/wiki/Q64 consistently doesn't load on beta wikidata

2020-05-04 Thread RhinosF1
RhinosF1 added a comment. @DannyS712: loads fine here TASK DETAIL https://phabricator.wikimedia.org/T249018 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: RhinosF1 Cc: RhinosF1, Nikerabbit, DannyS712, Addshore, Aklapper, darthmon_wmde, Nandana,

[Wikidata-bugs] [Maniphest] [Commented On] T249018: A revision of https://wikidata.beta.wmflabs.org/wiki/Q64 consistently doesn't load on beta wikidata

2020-05-04 Thread DannyS712
DannyS712 added a comment. Now just gives `Service Temporarily Unavailable Our servers are currently under maintenance or experiencing a technical problem. Please try again in a few minutes.` on the beta cluster with no more information TASK DETAIL

[Wikidata-bugs] [Maniphest] [Commented On] T249018: A revision of https://wikidata.beta.wmflabs.org/wiki/Q64 consistently doesn't load on beta wikidata

2020-04-01 Thread Addshore
Addshore added a comment. So, diffs actually load fine that relate to the revision. but the revision can not render (or seemingly save). When rendering the stacktrace for the memory allocation issue looks like: #0