Bug 280639 - Umbrello hangs when reverse engineering some C++ files
Summary: Umbrello hangs when reverse engineering some C++ files
Status: RESOLVED FIXED
Alias: None
Product: umbrello
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Ralf Habacker
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-23 11:38 UTC by openwoord
Modified: 2014-02-14 06:28 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In: 4.13.0

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description openwoord 2011-08-23 11:38:13 UTC 
Version:           unspecified (using KDE 4.4.5) 
OS:                Linux

I downloaded a set of C++ files ( svn co https://seman.svn.sourceforge.net/svnroot/seman seman ), then slightly modified some of the files, then imported all from the Source/ folder of the seman svn (Umbrello menu: Code/Import Project).

Umbrello hung on importing some file, became unresponsive to GUI events.

Umbrello version: 2.4.5

Reproducible: Didn't try

Steps to Reproduce:
1. svn co https://seman.svn.sourceforge.net/svnroot/seman seman
2. Start umbrello
3. Select in the umbrello menu: Code/Import Project; select seman svn/Source/ folder as input; (make sure that (Language: C++) is selected); press OK button.
4. Wait a few seconds.

Actual Results:  
Umbrello stops reacting to GUI events.

Expected Results:  
Should react to GUI events on time.

OS: Linux (i686) release 2.6.32-33-generic
Distribution: Ubuntu 10.04.*
Compiler: cc
Comment 1 Ken Standard 2013-07-08 15:35:30 UTC 
This bug still exists for Ubuntu 13.04 Umbrello 2.10.4. Import of any of the header files of the project xmlrpcpp will cause the app to become unresponsive as described before.
GNOME 3
Umbrello 2.10.4
CPU AMD 64 3800+ 1 Gb ram 15 Gb disk free
KDE Dev 4.10.4
Comment 2 Ralf Habacker 2014-02-12 00:26:49 UTC 
fixed with bug:330788
Comment 3 Ralf Habacker 2014-02-14 06:28:50 UTC 
(In reply to comment #2)
> fixed with bug:330788
wrong bug number, correct one is bug 330778