Staging: shows empty page in IE and Edge browsers

[saralavanip]

Steps

1.Visit https://staging.apinf.io v 0.51.0

Findings

Shows empty page

Operating system

• Windows 10 v 1511
• Windows 10 v 1703

Browsers

• Internet Explorer 11
• Edge v 25.10586.672.0

[bajiat]

@saralavanip Can you reproduce the error again, go to console and copy-paste what is shown on console? This is potentially related to another error. See: #3088.

[anarva]

Could not reproduce with Firefox v.56 or Chrome v.61 on Linux.

[saralavanip]

@bajiat , please find the console error messages in IE browser and Edge. screenshots below:

IE:
"SCRIPT5007: Array.prototype.toString: 'this' is null or undefined
bundle.js (104,24987)"

Edge:
" SCRIPT5007: Array.prototype.toString: 'this' is null or undefined
bundle.js (104,25523) "

Screenshot:

[bajiat]

I was able to reproduce the empty page problem in IE v. 11.674.15063. Did not get any console error, though.

Correction: after reloading page I got the console error:
"SCRIPT5007: Array.prototype.toString: 'this' is null or undefined"

[matleppa]

I also was able to reproduce it. IE 11.674.15063.0.
With console error.

[bajiat]

Same thing for apinf.io in IE: Empty page, zero console errors.

[bajiat]

Not able to reproduce in Edge.

Microsoft Edge 40.15063.674.0
Microsoft EdgeHTML 15.15063

[preriasusi]

Windows 10 + Firefox:

[matleppa]

@preriasusi also found this API in API catalog (apinf.io).
It seems, that because the name of API is in Chinese (or Japanese), the generation of slug has failed, thus the link being only https://apinf.io/apis

I wonder, whether these have some connection, because the error message was
Array.prototype.toString: 'this' is null or undefined

But what about error staging?

[matleppa]

Now I was able to reproduce the error in localhost.

IE 11.674.15063.0

92 errors.

[matleppa]

0.49.0

In release 0.49.0 there are no errors.

Release 0.50.0

In release 0.50.0 there is lot of new code, however, nothing seems to be related to both UI and swagger.
There is also Meteor version upgrade and many Meteor package updates.

Tracking changes after commits

After updating Meteor.js from 1.4.4.2 to 1.5.2 (commit 4989881) the errors appear.

Updating Meteor updates automatically following packages also.
accounts-base upgraded from 1.2.17 to 1.3.2
accounts-github upgraded from 1.2.1 to 1.3.0
accounts-password upgraded from 1.3.6 to 1.4.0
allow-deny upgraded from 1.0.5 to 1.0.6
babel-compiler upgraded from 6.18.2 to 6.20.0
boilerplate-generator upgraded from 1.0.11 to 1.2.0
ddp upgraded from 1.2.5 to 1.3.0
ddp-client* upgraded from 1.3.4 to 2.1.3
ddp-common upgraded from 1.2.8 to 1.2.9
ddp-server* upgraded from 1.3.14 to 2.0.2
dynamic-import added, version 0.1.1
ecmascript upgraded from 0.7.3 to 0.8.2
ecmascript-runtime upgraded from 0.3.15 to 0.4.1
ecmascript-runtime-client added, version 0.4.3
ecmascript-runtime-server added, version 0.4.1
ejson upgraded from 1.0.13 to 1.0.14
email upgraded from 1.2.1 to 1.2.3
localstorage upgraded from 1.0.12 to 1.1.1
meteor upgraded from 1.6.1 to 1.7.1
meteor-base upgraded from 1.0.4 to 1.1.0
minifier-js upgraded from 2.0.0 to 2.1.2
minimongo upgraded from 1.0.23 to 1.3.1
modules upgraded from 0.8.2 to 0.10.0
modules-runtime upgraded from 0.7.10 to 0.8.0
mongo upgraded from 1.1.17 to 1.2.0
mongo-dev-server added, version 1.0.1
npm-bcrypt upgraded from 0.9.2 to 0.9.3
npm-mongo upgraded from 2.2.24 to 2.2.30
promise upgraded from 0.8.8 to 0.9.0
reactive-dict upgraded from 1.1.8 to 1.1.9
shell-server upgraded from 0.2.3 to 0.2.4
standard-minifier-js upgraded from 2.0.0 to 2.1.1
webapp upgraded from 1.3.15 to 1.3.19

One guess

According to discussions found when searching: Array.prototype.toString: 'this' is null or undefined
The problem might be similar as in
zloirock/core-js#300

[Nazarah]

from @55
Suggestion 1: update meteor to 1.6 to release 51 to see if the problem goes away.
Suggestion 2: isolate this problem from development branch and make a release 51 if the problem takes too much time to solve

[matleppa]

2017-11-13
Researching suggestion 1. (update Meteor 1.6 to release 0.51.0)

• checked out release 0.51.0 (errors)

Upgrading Meteor to 1.6 (in Windows)

• requires new installer chocolatey
  • installed (slowly, success on second time)

Installing Meteor

• recommends installing a new version of Mongo database engine (Your development database is using mmapv1, the old, pre-MongoDB 3.0 database engine. You
  should consider upgrading to Wired Tiger, the new engine. The easiest way to do so in
  development is to run meteor reset. If you'd like to migrate your database, please
  consult https://docs.mongodb.org/v3.0/release-notes/3.0-upgrade/)
• is very slow, lots of error -4048 (operation not permitted)
  • Also other ones have had problems (https://forums.meteor.com/t/upgrade-to-1-6-failing/40184)
• on second time (after renaming ../appdata/local/.meteor to .meteor_old and creating a new .meteor) the installation seems to advance better
  • advancing slowly
  • is it stuck here: Downloading rajit:bootstrap3-datepick... \
    • did not take even ctrl-C
• after an hour a new command prompt and >meteor
  • is it this time stuck here: Building the application -
• after half an hour a new command prompt and >meteor
  • keeps throwing reference errors

W20171113-16:33:44.170(2)? (STDERR) ReferenceError: ShareJS is not defined
W20171113-16:33:44.172(2)? (STDERR) at sharejs-server.js (packages/mizzao:sharejs/sharejs-server.js:8:24)
W20171113-16:33:44.175(2)? (STDERR) at fileEvaluate (packages\modules-runtime.js:333:9)
W20171113-16:33:44.177(2)? (STDERR) at require (packages\modules-runtime.js:228:16)
W20171113-16:33:44.178(2)? (STDERR) at C:\Users\matleppa\api\apinf\platform.meteor\local\build\programs\server\packages\mizzao_sharejs.js:126:15
W20171113-16:33:44.180(2)? (STDERR) at C:\Users\matleppa\api\apinf\platform.meteor\local\build\programs\server\packages\mizzao_sharejs.js:132:3
W20171113-16:33:44.181(2)? (STDERR) at infos.forEach.info (C:\Users\matleppa\api\apinf\platform.meteor\local\build\programs\server\boot.js:414:13)
W20171113-16:33:44.182(2)? (STDERR) at Array.forEach ()
W20171113-16:33:44.185(2)? (STDERR) at C:\Users\matleppa\api\apinf\platform.meteor\local\build\programs\server\boot.js:413:9
W20171113-16:33:44.187(2)? (STDERR) at C:\Users\matleppa\api\apinf\platform.meteor\local\build\programs\server\boot.js:463:5
W20171113-16:33:44.189(2)? (STDERR) at Function.run (C:\Users\matleppa\api\apinf\platform.meteor\local\build\programs\server\profile.js:510:12)

• Stopped with ctrl-C.

• given: >meteor npm install

  • error: C:\Users\matleppa\api\apinf\platform\node_modules\bcrypt\build\bcrypt_lib.vcxproj(20,3): error MSB4019: The imported pr
    oject "C:\Microsoft.Cpp.Default.props" was not found. Confirm that the path in the declaration is correct, and
    that the file exists on disk.

• again: ReferenceError: ShareJS is not defined

  • going on...

[matleppa]

2017-11-14

Cont'd

Reinstalling ShareJS: meteor add mizzao:sharejs, meteor add mizzao:sharejs-ace

• stilll: ReferenceError: ShareJS is not defined

While installation (in this case $ meteor npm install --save bcrypt), an error message "error MSB4019: The imported pr
oject "C:\Microsoft.Cpp.Default.props" was not found"

$ meteor npm cache clean

After that command still:

• ReferenceError: ShareJS is not defined

[matleppa]

2017-11-16

Continuing again

• checkout for release 0.51.0
• Meteor upgrade to 1.6
  • again ShareJS error
    • discussion about it ShareJS object not exported? mizzao/meteor-sharejs#76
  • $ meteor add mizzao:sharejs-ace
    • however, still same shareJS error
  • $ meteor update
    • errors: packages/kurounin:pagination-blaze/client/template.html:7: Unexpected closing template tag
      .../if}}
    • not very promising, I would say...

[matleppa]

2017-11-17

What about downgrading Meteor version?

$ meteor --release 1.4.4.3

• lots of errors, trying to upgrade the Meteor version
• errors, referring to folder under 1.6.0
• deleting folders manually (so deep path, that problems in deletion)
• command meteor not recognized, points to 1.6.0...
• reinstalling meteor
• starting meteor (speed fails to meet my expectations, fortunately it is not a surprise...)
• after over an hour, a new attempt with command prompt with admin privileges...
• fetched newest version as default, so once again, let's degrade...1.5.3
• turn to worse, meteor does not start anymore
  • trying to uninstall and install again...

[matleppa]

2017-11-21

Struggle against Meteor continues

• Could not get Meteor to start yesterday. Perhaps the folder path has become too deep while unistalling and reinstalling?

• uninstalling Meteor via Control Panel still leaves /.meteor

• shortening the path with subst v: "beginning-of-path" did help, the path could be deleted

• new installation with Meteor installer

  • command meteor show meteor --> got stuck
  • new command prompt
  • meteor npm install...produced some bcrypt errors, as it usually does

• trying to start Meteor...messed up the command prompt window...

  • CTRL-c and new start for Meteor

    • First attempt produced errors, starting with "Error: ENOTEMPTY: directory not empty, rmdir 'C:\Users\matleppa\AppData\Local\Temp.tmp19divw\accounts-ui-1.1.9'"

  • let's see another try...

    • Again errors: "Error: ENOTEMPTY: directory not empty, rmdir 'C:\Users\matleppa\AppData\Local\Temp.tmp1gl6djw\arillo_flow-router-helpers-0.5.2"

  • let's kill Atom and try again...

  • After that it seemed, that Meteor started. Perhaps I've been able to reach same position, where I was a week ago! Jeeee!

• IE 11, v. 11.726.15063.0 with release 0.49.0 is OK

  • upgrading to release 0.50.0 (causes also Meteor to upgrade to 1.5.2)...

    • empty site and console log: SCRIPT5007: Array.prototype.toString: 'this' is null or undefined, bundle.js (104,24987)

    • same situation with apinf.io, staging.apinf.io. However, nightly.apinf.io is OK

    • errors: => Started MongoDB.
      Loading rajit:bootstrap3-datepicker@1... -
      <--- Last few GCs --->

[3984:001C82D8] 3524147 ms: Mark-sweep 583.5 (859.9) -> 578.5 (861.4) MB, 2270.1 / 4.1 ms allocation failure scavenge might not succeed
[3984:001C82D8] 3526403 ms: Mark-sweep 584.9 (861.4) -> 579.6 (862.4) MB, 2023.7 / 3.9 ms allocation failure scavenge might not succeed
[3984:001C82D8] 3528297 ms: Mark-sweep 585.9 (862.4) -> 580.7 (864.4) MB, 1589.0 / 4.3 ms allocation failure scavenge might not succeed

<--- JS stacktrace --->
Cannot get stack trace in GC.
FATAL ERROR: NewSpace::Rebalance Allocation failed - process out of memory

C:\Users\matleppa\AppData\Local.meteor\packages\meteor-tool\1.5.2\mt-os.windows.x86_32\dev_bundle\lib\node_modules\meteor-promise\promise_server.js:218
throw error
- let's try to start Meteor again after stopping some other applications...seemed to start.

• localhost: SCRIPT5007: Array.prototype.toString: 'this' is null or undefined + 88 other errors in log

  • try next release of Meteor: $ meteor update --release 1.5.3
    • same situation with Meteor 1.5.3, empty screen and error SCRIPT5007: Array.prototype.toString: 'this' is null or undefined
  • try next release of Meteor: $ meteor update --release 1.5.4
  • • localhost: SCRIPT5007: Array.prototype.toString: 'this' is null or undefined + 88 other errors in log

[matleppa]

2017-11-22

checking, whether a working combination can be found

• because nightly seems not to suffer from this problem, is it possible, that with latest content of develop branch may contain some fixes, which accidentally help here also?

• Meteor 1.5.2 + branch /develop

  • suggests installing some packages: meteor npm install --save chart.js json2csv select2 select2-bootstrap-theme

• installed and a new Meteor start

  • same outcome: SCRIPT5007: Array.prototype.toString: 'this' is null or undefined

• trying to downgrade Meteor to 1.4.4.2

  • $ meteor update --release 1.4.4.2

[anarva]

An imported swagger UI bundle JavaScript file which has been minified caused the problem - the compressed product was not compatible with IE. I have submitted a code fix for review.