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

Spontaneous exits - attempting to isolate #177

Open
emyoulation opened this issue May 30, 2022 · 7 comments
Open

Spontaneous exits - attempting to isolate #177

emyoulation opened this issue May 30, 2022 · 7 comments
Labels
bug Something isn't working

Comments

@emyoulation
Copy link

Just a heads up.

I've had 2 spontaneous exits today. 1 with my 48,000 person Tree and another with the Example.gramps tree. Since the console immediately closed, I have no diagnostics.

Both while were while switching to a CardView view mode. There was about 30 seconds of unresponsive GUI without changing Navigator or Toolbar or view from the Previous view mode, then the exit.

I will revert to launching from the command prompt and try to isolate. More late.

@cdhorn
Copy link
Owner

cdhorn commented May 30, 2022

I am thinking this may be memory related unless I have some kind of bug that causes a recursion.

@cdhorn cdhorn added the bug Something isn't working label May 30, 2022
@emyoulation
Copy link
Author

emyoulation commented May 31, 2022

Just after starting Gramps (with it recalling the a 20-person tree for Gramps developer contacts that was previously loaded), selected the People category Person CardView mode. If CardView remembers Template selection, it would've been "selfish template" shared previously)

Threw an error and froze on "cancel" out of the Gramps Error Dialog

C:\Program Files\GrampsAIO64-5.1.5>gramps
2022-05-31 11:05:24.439: WARNING: dummydb.py: line 1420: database is closed
render_page: I0000010 0.43599653244018555
2022-05-31 11:06:27.996: ERROR: grampsapp.py: line 174: Unhandled exception
Traceback (most recent call last):
  File "C:\Program Files\GrampsAIO64-5.1.5\gramps\gui\views\pageview.py", line 186, in set_page_slider
    vp_ch = side_ch[0].get_children()  # Gtk Viewport child
IndexError: list index out of range

@emyoulation
Copy link
Author

Repeated with Example.gramps -- got an error but no freeze upon Cancel and the Person CardView renders... but with the default template

84729: ERROR: grampsapp.py: line 174: Unhandled exception
Traceback (most recent call last):
  File "C:\Program Files\GrampsAIO64-5.1.5\gramps\gui\views\pageview.py", line 186, in set_page_slider
    vp_ch = side_ch[0].get_children()  # Gtk Viewport child
IndexError: list index out of range

@emyoulation
Copy link
Author

Selfish template is missing from the GUI... because I had DELETED the .ini from the Gramps51 folder yesterday in preparation to do a Import Template test.

So, switching to a CardView didn't fail gracefully when the selected Template .ini was missing in action

@cdhorn
Copy link
Owner

cdhorn commented Jun 10, 2022

Ah! I can reproduce the set_page_slider exception.

I took working tree, viewed all the categories with LastChanged Gramplet active. Shutdown Gramps. Renamed the last_changed.gpr.py to a .old so it would not load, restarted Gramps. The last changed gramplet config was still in all the sidebar.ini though. The initial category on start loaded just fine, but then each category I selected triggered the error as it's trying to setup a Gramplet that is no longer loaded and available.

So that's indeed an issue in Gramps core in pageview.py or elsewhere.

@emyoulation
Copy link
Author

So it needs a de-registration as a counterpoint to the Registration of plugins?

A scan of all the .ini to look for references to add-ons that are not in the freshly updated register.

(And possibly split bars invalid positions that exceed width/height of the target window.

Also problematic are custom filters that might use unregistered/out-of-revision addon rules.)

@cdhorn
Copy link
Owner

cdhorn commented Jun 12, 2022

If deregistered cleanly in Gramps, or if you used plugin manager and uninstalled, it would be fine. The issue comes up when you go yanking the config out under the covers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants