-
Notifications
You must be signed in to change notification settings - Fork 93
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash pivot-menu #310
Comments
Sry, I didn't expect, there's an stable version of the app, but found it, after reinstalling. The stable version also has the same bug. |
Hi there, |
Hi, The first logfile is from the beta and the second one is from the stable version. Both have the same behavior, but I´m not sure, if I can open the povit menu, if I add a script in the stable version. Sry, if something is unclear. Let me know what exactly you need and I will provide you as much information, as possible. Thanks for your work and support :) |
Thanks for confirming. So I would say that's two different crashes, though both happening on the Pivot page. I just published a new beta release which (hopefully) fixed the crash of an empty Pivot (but not the other = the bug you initially reported in this issue). |
I think i know what it is.
|
Absolutely genius. I didn't get it, that I removed the profile from one of my scripts, because I didn't see, there's an option to deactivate the script. I assigned the profile to the script in my beta version and now it works fine. Many thanks to you. 😊 I would close the issue, but I think it's better to repair this little bug, if it is little. |
That's strange. I accidentally reproduced it on my side, but after deleting some Scripts, I can no longer reproduce it...? I would suspect this being a problem in GraphView, because the stacktrace only contains code in GraphView (particularly |
You right. One script is not enough. I made a second one as above but with a connected profile. |
One script is enough, at my side. If I remove the profile from only one script, the app crashes at the time I open the povit menu. I recreated the crash with different profiles. Both are after removing the profile and trying to open the povit menu. After relaunching the app and add the profile back to the script, all works fine. And sorry, I'm not so deep into programming, but debugging and testing is just fine and I'm happy, if I can help in any way. P.S.: Also, I will reinstall my whole system to another ROM and more recent kernel, but it's the same kernel. I will check, if the problem occurs there too, but can take some days, have a lot of stress with work and some projects from myself. |
Okay, I've an update for you. ROM: Evolution X 4.0 | Official Raser version: 0.8-pre3-beta5 Now, I can open the povit menu without any problems. It doesn't if I've a profile assigned to the script or not. I will test later, if the problem behaves on the stable version and maybe on other older beta versions, which u should do, to sort out the problem. Maybe it was a huge bug on my end, I don't know. If you need any further informations, let me know it and I will help you 😊 |
Thanks @idealist1508 and @PsyEng. I did some tests and believe this is indeed a problem of the GraphView library, as you can see in the (back-)referenced issue (from GitHub). |
You're welcome, I hope the bug will get fixed fast, but, like I said, at my end, it's fixed now, but I believe, you only got a workaround, which don't solve the problem by itself. |
I've found the next bug -.- Same behavior like the last time, but different way. This time, it was an accident. P.S.: Maybe you will rename the log files by itself to "logs_0000.txt", because Github doesn't allow uploads of csv files |
I closed the issue, it's not updated since over a year and I don't use Easter anymore. If someone whish to re-open it, you're welcome. |
Describe the bug
Open the Povit-Menu will end in a crash, it doesn't matter if I clear cache or something else. Errorlog is always 100% the same.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Open the Povit-Menu^^
Error log:
2020_01_17_16_40_35.log
Extra phone information:
The text was updated successfully, but these errors were encountered: