Skip to content
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

Closed
PsyEng opened this issue Jan 17, 2020 · 14 comments
Closed

Crash pivot-menu #310

PsyEng opened this issue Jan 17, 2020 · 14 comments
Labels
bug General label for all bugs (i.e. things not working as intended) upstream (?) Upstream (library) issue (or likely that)

Comments

@PsyEng
Copy link

PsyEng commented Jan 17, 2020

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:

  1. Go to main screen
  2. Click on bacon icon
  3. Click on Povit-Menu
  4. See errorlog

Expected behavior
Open the Povit-Menu^^

Error log:
2020_01_17_16_40_35.log

Extra phone information:

@PsyEng PsyEng added the bug General label for all bugs (i.e. things not working as intended) label Jan 17, 2020
@PsyEng
Copy link
Author

PsyEng commented Jan 17, 2020

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.

2020_01_17_20_12_30.log

@renyuneyun
Copy link
Owner

renyuneyun commented Jan 18, 2020

Hi there,
I think they are two different bugs (as you may already be aware in #306 ).
The bug you reported is really strange... Can you confirm is there any Scripts (see the Data section) already? Or, does this happen on a new / empty installation?

@PsyEng
Copy link
Author

PsyEng commented Jan 18, 2020

Hi,
I used the app, made some scripts and then added a script to autostart Spotify and resume play. After this, the povit menu was completely broken. It doesn´t matter, if I reinstall the app or use my old data. Clear cache or anything else, doesn´t do anything.

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 :)

@renyuneyun
Copy link
Owner

renyuneyun commented Jan 18, 2020

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).
Please could you post another log file if Easer still crashes? This release should have a better log file, with method names not being obfuscated.

@idealist1508
Copy link
Contributor

I think i know what it is.
Here are the steps to reproduce:

  • Create some bondition for example Battery Level
  • Create Script with this Condition but without any Profile
  • Change to Pivot View => App Crash

@PsyEng
Copy link
Author

PsyEng commented Jan 19, 2020

I think i know what it is.
Here are the steps to reproduce:

* Create some bondition for example Battery Level

* Create Script with this Condition but without any Profile

* Change to Pivot View => App Crash

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.

@renyuneyun
Copy link
Owner

renyuneyun commented Jan 28, 2020

That's strange. I accidentally reproduced it on my side, but after deleting some Scripts, I can no longer reproduce it...?
Even after I removed all Scripts and followed @idealist1508 's example, the problem does not appear.

I would suspect this being a problem in GraphView, because the stacktrace only contains code in GraphView (particularly SugiyamaAlgorithm), but can not be exactly sure.

@renyuneyun renyuneyun added more-info-needed Needs more input to pin down or solve the issue RFC / Discussion Wanted Request For Comment labels Jan 28, 2020
@idealist1508
Copy link
Contributor

You right. One script is not enough. I made a second one as above but with a connected profile.
Here is a exported data: Easer.2020-01-29.07_11_34.zip

@PsyEng
Copy link
Author

PsyEng commented Jan 29, 2020

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.
Here are both files. If you need more, let it know me.
2020_01_29_20_20_08.log
2020_01_29_20_22_26.log

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.

@PsyEng
Copy link
Author

PsyEng commented Feb 5, 2020

Okay, I've an update for you.
I've updated my system:

ROM: Evolution X 4.0 | Official
Build: QQ1B.200105.004
Kernel: 4.14.168-iMMENSITY #1 Tue Jan 28 10:38:29 UTC 2020

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 😊

@renyuneyun
Copy link
Owner

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).
Let's see how that goes and hope it will be solved soon.

@renyuneyun renyuneyun added upstream (?) Upstream (library) issue (or likely that) and removed RFC / Discussion Wanted Request For Comment more-info-needed Needs more input to pin down or solve the issue labels Feb 8, 2020
@PsyEng
Copy link
Author

PsyEng commented Feb 12, 2020

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.
Nice to see activity.

@PsyEng
Copy link
Author

PsyEng commented Mar 3, 2020

I've found the next bug -.-

Same behavior like the last time, but different way. This time, it was an accident.
I created a script, which has two child scripts with a profile. Then I unlinked the main script, from the child scripts and the app crashed.
Log will be append, questions are welcome.

logs_0.csv.txt

P.S.: Maybe you will rename the log files by itself to "logs_0000.txt", because Github doesn't allow uploads of csv files

@PsyEng PsyEng closed this as completed Jun 29, 2021
@PsyEng
Copy link
Author

PsyEng commented Jun 29, 2021

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug General label for all bugs (i.e. things not working as intended) upstream (?) Upstream (library) issue (or likely that)
Projects
None yet
Development

No branches or pull requests

3 participants