-
Notifications
You must be signed in to change notification settings - Fork 17
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
Outline crash at startup #39
Comments
Finally, this trace does not help me....sorry |
You might consider adding a trace at function exit for set_content_inset. Then at the exit of any function that calls set_content_inset -- that way you can isolate which section of code is crashing. Once you know it is between the exit of set_content_inset and the exit of some other function, you can add line by line traces in the questionable section |
I think the error is somewhere starting from row 3033 to end of function tableview_cell_for_row. It seems that height_for_cell_row must get called either in parallel or from cell_from_row -- so that's why content_inset is shown twice in a row -- once from the height function and once in th cell function. So segfault must be happening near the scrolling code which caused you problems before ... Just add some more trace logging in that area. |
@JonB I would like to be sure that the crash occurs each time there before. |
@ifuchs please, try to reproduce and tell us if same trace |
Just crashed again. Here is outline.trace 20210917 165610.425576 setup_tableview_swizzle |
|
Can you please stop tagging me in this. |
Oops -@cvpe note wrong name on GitHub :/. @cvpe, it seems like if the only reason you are using a new object every text view is to get the row, you could also do that by attaching the row as an attribute to the text view, which you get as first responder. Since your accessory views never get deleted, you might just be running out of memory. (There is a way, iirc, to get the pyObject of the SUITextView object, though you have to change the restype and encoding) |
@jsbain you're right about sharing (if possible) the same input accessory view, and I'll try, but I don't think this is a problem. The trace shows that the crash occurs after only ONE row displayed (only once call to textview_cell_for_row), at begin of the run. And that would not explain that if @ifuchs runs another script before, the problem does not appear. @ifuchs could you retry witH the v01.00 which has more detailed trace in textview_cell_for_row |
@jsbain "content_inset is shown twice in a row", for two different TextView objects, thus entirely normal. |
Outline.trace
20210917 122744.565916 setup_tableview_swizzle
20210917 122744.572534 main
20210917 122744.573498 init
20210917 122744.620835 get_screen_size
20210917 122744.623932 get_screen_size
20210917 122744.794352 button_undo_enable
20210917 122744.796551 button_redo_enable
20210917 122744.814525 set_key_event_handlers
20210917 122744.830051 tableview_number_of_rows
20210917 122744.832999 layout
20210917 122744.833339 get_screen_size
20210917 122744.834677 tableview_number_of_rows
20210917 122745.817715 init2
20210917 122745.820967 button_files_action
20210917 122745.825080 files_action
20210917 122745.829540 set_font
20210917 122745.834794 tableview_number_of_rows
20210917 122745.837691 set_font
20210917 122745.842580 tableview_number_of_rows
20210917 122745.845454 set_font
20210917 122745.850299 tableview_number_of_rows
20210917 122745.853140 pick_open_callback
20210917 122745.939202 set_font
20210917 122745.940208 set_font
20210917 122745.941039 prms_save
20210917 122745.942142 open_log
20210917 122745.942769 undo_save
20210917 122745.945251 tableview_number_of_rows
20210917 122745.945649 tableview_cell_for_row
20210917 122745.947200 tableview_height_for_section_row
20210917 122745.953747 set_content_inset
20210917 122745.964020 set_content_inset
The text was updated successfully, but these errors were encountered: