locked
Got a "Array length must be a finite positive integer" error, does it ring bells to anyone?

    Question

  • Hi all,

    Here is one exception sent by one of my users through my error reporting system:

    Array length must be a finite positive integer
    RangeError: Array length must be a finite positive integer
       at repeat (ms-appx://microsoft.winjs.2.0/js/ui.js:22528:9)
       at addToGroup (ms-appx://microsoft.winjs.2.0/js/ui.js:30270:25)
       at newGroup (ms-appx://microsoft.winjs.2.0/js/ui.js:30291:25)
       at VirtualizeContentsView_createChunk (ms-appx://microsoft.winjs.2.0/js/ui.js:30307:25)
       at Anonymous function (ms-appx://microsoft.winjs.2.0/js/ui.js:30509:29)
       at notifySuccess (ms-appx://microsoft.winjs.2.0/js/base.js:1550:21)
       at enter (ms-appx://microsoft.winjs.2.0/js/base.js:1232:21)
       at _run (ms-appx://microsoft.winjs.2.0/js/base.js:1448:17)
       at _completed (ms-appx://microsoft.winjs.2.0/js/base.js:1416:13)
       at notifySuccess (ms-appx://microsoft.winjs.2.0/js/base.js:1550:21)

    I really don't have any clue about what happened, does anyone ever encountered such an error?

    Thanks,
    Pierre

    Wednesday, April 16, 2014 11:35 AM

Answers

  • Hello Pierre,

    This sounds like we may have a problem. We are going to need more information from you to really be able to dig in and see if we can get a workaround or if it is a defect in the Microsoft codebase we certainly want to get it fixed.

    The fastest way for us to help you get this resolved is if we work together one-on-one. Please open a support incident by going here: http://aka.ms/storesupport

    Once you get an incident opened we should be able to quickly figure out what is happening.

    Thanks,

    James


    Windows SDK Technologies - Microsoft Developer Services - http://blogs.msdn.com/mediasdkstuff/

    Friday, April 18, 2014 9:04 PM
    Moderator

All replies

  • Hello,

    This issue has been reported previously but does not occur with any regular frequency. The root cause is still unknown. Reports of this issue have virtually disappeared with the release of 8.1. It usually occurs when the app is under stress, i.e. when a large number of manipulations are occurring.

    Our current recommendation is to make sure your app targets 8.1 and ask your customers to install the 8.1 update. This will hopefully resolve the issue. If you are still seeing this error on 8.1 update with regular frequency please let us know and we will work with you to investigate further.

    I hope this helps,

    James


    Windows SDK Technologies - Microsoft Developer Services - http://blogs.msdn.com/mediasdkstuff/

    Thursday, April 17, 2014 12:14 AM
    Moderator
  • Hello James,

    Thank you for your answer.

    Unfortunately, it happens in Windows 8.1 since the reports I received were sent from a version of my app that only supports Windows 8.1 runtime.

    I've received 5 reports about this RangeError last weekend (and deactivated error reports since monday so it may still occur) from 5 different users, the StackTrace slightly differs, do you want me to post the 5 of them here?

    Giving the fact that it happens in two different pages of the app using the same root DataAdapter and that the Trace is talking about VirtualizeContents, I'd say that the problem lies within the DataAdapter mecanism. When these errors were reported in Windows 8, did you find a workaround to this problem?

    Thanks for your help.

    Pierre

    Thursday, April 17, 2014 8:24 AM
  • I've got 12 more users who encountered this error yesterday, does anyone have a clue on what is going on?
    Friday, April 18, 2014 3:31 PM
  • Hello Pierre,

    This sounds like we may have a problem. We are going to need more information from you to really be able to dig in and see if we can get a workaround or if it is a defect in the Microsoft codebase we certainly want to get it fixed.

    The fastest way for us to help you get this resolved is if we work together one-on-one. Please open a support incident by going here: http://aka.ms/storesupport

    Once you get an incident opened we should be able to quickly figure out what is happening.

    Thanks,

    James


    Windows SDK Technologies - Microsoft Developer Services - http://blogs.msdn.com/mediasdkstuff/

    Friday, April 18, 2014 9:04 PM
    Moderator
  • Hello James,

    Ok, that's great, I'll do that next week, I'll keep you posted.

    Thanks!

    Friday, April 18, 2014 9:31 PM
  • Hello James,

    I'm not sure I'm going on the correct page but when I want to post my support incident, the website asks me to pay for support... Is it normal or did I make a mistake?

    Thanks,

    Pierre

    Tuesday, April 22, 2014 12:02 PM
  • Hello Pierre,

    If you are an MSDN subscriber you should have two free support incidents with your subscription. If you are not an MSDN subscriber we do require a small fee for processing and routing your request. If the problem does end up being a defect in the Microsoft codebase then we will refund you the processing fee.

    I'm looking forward to working more closely with you. Let me know if you have any other questions.

    Thanks,

    James


    Windows SDK Technologies - Microsoft Developer Services - http://blogs.msdn.com/mediasdkstuff/

    Thursday, April 24, 2014 11:21 PM
    Moderator