After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 341757 - Crash during Since Last Run
Crash during Since Last Run
Status: VERIFIED DUPLICATE of bug 343405
Product: GnuCash
Classification: Other
Component: Scheduled Transactions
git-master
Other Linux
: Normal critical
: ---
Assigned To: Chris Shoemaker
Josh Sled
Depends on: 343405
Blocks:
 
 
Reported: 2006-05-14 16:38 UTC by Tim Wunder
Modified: 2018-06-29 21:04 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Tim Wunder 2006-05-14 16:38:25 UTC 
While updating an SX, gnucash crashed (svn 514032).
Edited an SX, then tried to process it in the SLR. The SX had just been edited, and has a single variable in it.
I typed in the variable amount, pressed Enter on the keyboard, then clicked Forward. Gnucash crashed. I am unable to duplicate the crash using these steps, but am posting the backtrace in case someone sees something that needs fixing.
I had processed several (6-8) SXs thru a couple iterations of the SLR without any problem prior to the crash.

Backtrace was generated from '/opt/gnucash/bin/gnucash'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1208780576 (LWP 14801)]
0x007bc402 in ?? ()

+ Trace 68218

Thread 1 (Thread -1208780576 (LWP 14801))

  • #0 ??
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 gtk_tree_model_get_valist
    from /usr/lib/libgtk-x11-2.0.so.0
  • #5 gtk_tree_model_get
    from /usr/lib/libgtk-x11-2.0.so.0
  • #6 sort_by_string
    at gnc-tree-view-account.c line 287 






Comment 1


Chris Shoemaker





          2006-05-30 20:16:20 UTC
        



I know it's been a while, but do you remember if you had recently created or deleted an account?






Comment 2


Chris Shoemaker





          2006-05-30 20:24:37 UTC
        



Or, here's another idea/question.  Maybe you had the FilterBy setting for the account tree set to hide-zero-balance-accounts.  Then, maybe the transaction you created from the SX was the first transaction in the account, and so the account became non-zero balance.  So maybe frame 14 is the filter model emitting row_inserted because there's a newly visible account.  Possible?






Comment 3


Josh Sled





          2006-05-30 20:35:05 UTC
        



(In reply to comment #2)
> Or, here's another idea/question.  Maybe you had the FilterBy setting for the
> account tree set to hide-zero-balance-accounts.  Then, maybe the transaction
> you created from the SX was the first transaction in the account, and so the
> account became non-zero balance.  So maybe frame 14 is the filter model
> emitting row_inserted because there's a newly visible account.  Possible?

FWIW, I can't reproduce according to this theory.  The now-non-zero account simply becomes visible.







Comment 4


Tim Wunder





          2006-05-31 02:03:55 UTC
        



all I remember about it was what's written, sorry. I do know that I haven't had the SLR crash on me in quite some time (probly since 5/14/06). Although I haven't edited many SX's either.






Comment 5


Chris Shoemaker





          2006-06-01 13:51:03 UTC
        



This _may_ have been fixed by r14283 and r14285.  At the very least, that fix has been shown to correct filter-model behavior for some gtk+ versions.  Can you tell what version of gtk+ you were using here?






Comment 6


Chris Shoemaker





          2006-06-01 14:17:04 UTC
        



Another possible explanation is that the account tree view was sorted on one of the balance columns, and creating the sx changed the sort order of that account.

But, I really think the scenario in comment #2 best explains this:




+
Trace
    68583






    

  • 
#14
gtk_tree_model_row_inserted

    
                from
                /usr/lib/libgtk-x11-2.0.so.0

    

    • 

  • 
#15
gtk_tree_model_filter_convert_iter_to_child_iter

    
                from
                /usr/lib/libgtk-x11-2.0.so.0

    

    • 

  • 
#16
gtk_marshal_VOID__UINT_STRING

    
                from
                /usr/lib/libgtk-x11-2.0.so.0

    

    • 

  • 
#17
g_closure_invoke

    
                from
                /usr/lib/libgobject-2.0.so.0

    

    • 

  • 
#18
g_signal_stop_emission

    
                from
                /usr/lib/libgobject-2.0.so.0

    

    • 

  • 
#19
g_signal_emit_valist

    
                from
                /usr/lib/libgobject-2.0.so.0

    

    • 

  • 
#20
g_signal_emit

    
                from
                /usr/lib/libgobject-2.0.so.0

    

    • 

  • 
#21
gtk_tree_model_row_changed

    
                from
                /usr/lib/libgtk-x11-2.0.so.0

    

    • 

  • 
#22
gnc_tree_model_account_event_handler

    
                at gnc-tree-model-account.c
                  line
                  1567

    

    • 








the account tree model only emitted row_changed (frame #21), but the filter model emits row_inserted (frame #14).

This isn't strictly a dup of bug #343362, since you weren't creating an account, but I'm convinced it's part of the same bug-complex.  I'm closing this as a dup of bug #343405, which seems resolved by r14285.



*** This bug has been marked as a duplicate of 343405 ***






Comment 7


André Klapper





          2006-11-27 18:33:29 UTC
        



*** Bug 379371 has been marked as a duplicate of this bug. ***






Comment 8


John Ralls





          2018-06-29 21:04:16 UTC
        



GnuCash bug tracking has moved to a new Bugzilla host. This bug has been copied to https://bugs.gnucash.org/show_bug.cgi?id=341757. Please update any external references or bookmarks.