farfromrefug
commented
3 years ago @cjohn001 i would say the error is with a listview inside your tabs. For some reason it tries to add 140362783383168 items to the listview.
Closed cjohn001 closed 3 years ago
farfromrefug
commented
3 years ago @cjohn001 i would say the error is with a listview inside your tabs. For some reason it tries to add 140362783383168 items to the listview.
cjohn001
commented
3 years ago Well, I am only using nativescript-community/ui-collectionview on the page. I have also ui-collectionview items on other pages without a ui-material-tabs component and their they work perfectly fine. Therefore, I expected it to be ui-material-tabs, or it is some inference between those plugins. Do you think the issue should better be moved to ui-coolectionview? And can you do this?
I am using the most recent version and tried the older version as well, as I suspected it to be the source of the problem as well "@nativescript-community/ui-collectionview": "4.0.43", "@nativescript-community/ui-collectionview": "4.0.42",
farfromrefug
commented
3 years ago @cjohn001 honestly not sure who is responsible for triggering the issue but your error message clearly talks of uicollectionview. Can you create a repoducable example ?( really sorry to keep on asking it but that is the only real way to investigate this)
cjohn001
commented
3 years ago @farfromrefug: Well, I understand. With the description I gave it is clear to me that it is very difficult to reason. I will try to replicate the issue. My major hope was that you might be able to give me a hint how I could enable some kind of tracing to get more detailed info when thinks break. But probably there is no additional option I am not aware of :)
cjohn001
commented
3 years ago @farfromrefug: I got some help in the forum in order to debug the issue further. It is not related to the collection view. There exists an option in nativescript.config.ts which you can set to false in order to obtain a stacktrace.
discardUncaughtJsExceptions: false
This gives me the following problem when navigating away from the page with the materialtabs:
I think this is the problem: file: node_modules/@nativescript-community/ui-material-tabs/tabs.ios.js:148:0 JS ERROR TypeError: null is not an object (evaluating 'this.tabBar.frame')
The full stack trace:
Fatal JavaScript exception - application has been terminated.
Native stack trace:
1 0x10558162e NativeScript::reportFatalErrorBeforeShutdown(JSC::ExecState, JSC::Exception, bool)
2 0x1055c23a8 NativeScript::FFICallback
And the attached image shows the relevant code:
I unfortunately do not understanding what is happening there. Like I mentioned, the issue appears when navigating away from the page. In the debugger I could observe that
this.tabBar = null
when the app crashes. But more interesting is, that most of the time (which I would expect should be the normal behavior) on leaving the page, this code block is not executed at all. I am wondering why a layout cycle is called than in certain situations when the page is left. I assume this is the real problem. Maybe we can simply add an additional test on line 145
if(owner.testStript && this.tabBar) ?
farfromrefug
commented
3 years ago @cjohn001 thanks i know understand the issue. The view controller try to layout its subviews after the tabbar have been released. It should be easy to fix. I wonder if this is another issue though as it is not the same error message. Will fix tonight or tomorrow.
cjohn001
commented
3 years ago @farfromrefug: The error with the tabbar is the one which I observed in the latest version of the plugin -ui-material-tabs": "5.3.19" As I could only see the single line error message: NativeScript discarding uncaught JS exception!
I downgraded to "5.3.15". From which the stacktrace with the rows was obtained from. I will further have an eye on the topic if I see the issue from the old plugin again. I indeed have another issue with the UICollectionView. But it is not related to the issue here, therefore I will provide an extra issue in its repository later the day. Need to prepare some stuff first in order to be able to show the problem.
farfromrefug
commented
3 years ago @cjohn001 just released 5.3.20 which should fix it!
cjohn001
commented
3 years ago I can confirm the bug is fixed. Thank you very much!
Which platform(s) does your issue occur on?
Please, provide the following version numbers that your issue occurs with:
node_modules/@nativescript/core/package.jsonfile in your project)"devDependencies": { "@angular/compiler-cli": "~12.2.2", "@graphql-codegen/cli": "^1.20.1", "@graphql-codegen/fragment-matcher": "^2.0.1", "@graphql-codegen/introspection": "^1.18.1", "@graphql-codegen/typescript": "^1.21.1", "@graphql-codegen/typescript-apollo-angular": "~2.3.1", "@graphql-codegen/typescript-operations": "^1.17.15", "@nativescript/android": "8.0.0", "@nativescript/ios": "JSC", "@nativescript/types": "~8.0.1", "@nativescript/webpack": "^5.0.0-rc.4", "@ngtools/webpack": "~12.2.0", "@types/d3-ease": "^2.0.0", "@types/intl": "^1.2.0", "@types/node": "^13.13.19", "@types/uuid": "^8.3.0", "codelyzer": "^6.0.1", "keycloak-request-token": "^0.1.0", "sass": "^1.37.5", "ts-node": "^9.1.1", "tslint": "^6.1.3", "typescript": "~4.2.0" },
Please, tell us how to recreate the issue in as much detail as possible.
Unfortunately, the bug seems to be not easy to reproduce. It seems to be a runtime issue which not always appears. The problem: I have a page with the material tabs control including 4 tab pages. Everything is working fine. When I try to navigate away to a new page I randomly see the following error message without a stack trace.
NativeScript discarding uncaught JS exception!
The JSC runtime does not brake but just seems to ignore the issue. With the new v8 runtime the app crashes instead.
The just described behavior appears with "5.3.19" of the plugin. I downgraded to "5.3.15" where I see the same bug. But here I got an additional stacktrace which is given below:
CONSOLE LOG file: node_modules/@angular/core/fesm2015/core.js:28039:0 Angular is running in development mode. Call enableProdMode() to enable production mode. NativeScript discarding uncaught JS exception! NativeScript discarding uncaught JS exception! Fatal JavaScript exception - application has been terminated. Native stack trace: 1 0x10840d62e NativeScript::reportFatalErrorBeforeShutdown(JSC::ExecState, JSC::Exception, bool) 2 0x10845f524 -[TNSRuntime executeModule:referredBy:] 3 0x107645093 main 4 0x7fff2025abbd start JavaScript stack trace: UIApplicationMain(file: node_modules/@nativescript/core/application/index.ios.js:336:0 at run(file: node_modules/@nativescript/core/application/index.ios.js:336:0 at runNativeScriptAngularApp(file: node_modules/@nativescript/angular/fesm2015/nativescript-angular.js:564:19 at ./src/main.ts(file: src/src/main.ts:23:25 at webpack_require(file: src/webpack/bootstrap:19:0 at webpack_exec(file:///app/bundle.js:36557:58) at file:///app/bundle.js:36558:127 at file: src/webpack/runtime/startup entrypoint:6:0 at file:///app/bundle.js:36558:48 at anonymous(file:///app/bundle.js:36563:3) at evaluate([native code]) at moduleEvaluation([native code]) at [native code] at asyncFunctionResume([native code]) at [native code] at promiseReactionJob([native code]) JavaScript error: file: node_modules/@nativescript/core/application/index.ios.js:336:0 JS ERROR Error: Failed to allocate data stores for 140362783383168 rows in section 0. Consider using fewer rows
@farfromrefug : I know it is very unlikely that you will find the issue with the given details. I am wondering, if Nativescript has some kind of tracing functionality which I could activate to get more information like a stacktrace for the most recent plugin version. It seems that there is some uninitialzed variable involved (rows?).