#1194 keepass heavily uses CPU and freezes machine while loading kdbx

KeePass_2.x
closed
nobody
2.24 (1)
5
2014-10-04
2013-12-17
Daniel
No

I am using 2.24 version with mono under fedora 19 and the Gnome desktop, when I open my kdbx file and search it blocks the complete machine (quad-core, 8G Memory)
I have 508 entries in the main database file (mostly unsorted because I imported them from firefox)
after a while the data shows and everything works as normal.I have attached my output of the top command which shows that mono uses 130% of my CPU just after I click the main folder (within the red area). The screen stays like this until the entries show and I cannot even move another window or activate anything else, after that period everything is back to normal, but everytime after a search for example the same happens.

I'll try to separate the entries into several groups (like banking etc,) and report back then.

This happened after I upgraded from 2.23 to 2.24,

1 Attachments

Discussion

  • Daniel

    Daniel - 2013-12-17

    The same freeze happens, when I move entries into another group/folder
    but not when I delete entries

    I cannot select multiple database entries and move them as a block into a group, when I right click on the entry, the menu does not work, (this is new today, I try to reload KeePass)

     
    Last edit: Daniel 2013-12-17
  • Paul

    Paul - 2013-12-18

    I'd say it's a mono thing, not a KeePass bug. To be sure try opening the database on a Windows machine.

    cheers, Paul

     
  • Dominik Reichl

    Dominik Reichl - 2013-12-25
    • status: open --> closed
     
  • Dominik Reichl

    Dominik Reichl - 2013-12-25

    Mono is displaying/handling the UI controls (list views, tree views, text boxes, ...). I don't think there's anything KeePass could do to improve the performance of standard UI interactions.

    Best regards,
    Dominik

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks