Opened 12 years ago
Closed 11 years ago
#2145 closed defect (worksforme)
OMEdit executes without end
| Reported by: | Owned by: | Adeel Asghar | |
|---|---|---|---|
| Priority: | high | Milestone: | 1.9.1 |
| Component: | OMEdit | Version: | trunk |
| Keywords: | Cc: | Per Östlund |
Description
Mike Thomson wrote in https://www.openmodelica.org/index.php/forum/topic?id=809
Steps taken: I open OMEdit I open the model (which runs OK in OMShell) I can Instantiate Model & Check Model OK I click the Simulate icon and leave the settings Start 0.0, Stop 1.0; dassl; Tol 0.000001; no flags then click on the Simulate button A progress bar shows at 100% for a moment The OMEdit view changes to Plotting Then nothing more can be done in the OMEdit window - it will not respond to any mouse or keyboard commands The System Monitor shows that OMEdit is processing 100% and continues till I get bored of waiting and kill it
reproducible on OMEdit 1.9.0 beta4+dev (r15767)
https://www.openmodelica.org/index.php/forum/topic?id=897
Attachments (2)
Change History (32)
by , 12 years ago
follow-up: 3 comment:2 by , 12 years ago
Replying to sjoelund.se:
I think Per has 4.8 in arch linux so he could have a look and see if the model is problematic.
Works fine for me with qt4 4.8.4 and qwt 6.0.2.
comment:3 by , 12 years ago
Replying to perost:
Replying to sjoelund.se:
I think Per has 4.8 in arch linux so he could have a look and see if the model is problematic.
Works fine for me with qt4 4.8.4 and qwt 6.0.2.
I have qt4 4.8.2 and qwt 5.2.2
follow-ups: 5 7 comment:4 by , 12 years ago
And my qwt was also 5.2.2... So... What did Adeel do? :)
(Also, were OMPlot and OMEdit compiled with gcc 4.4 or 4.7?)
comment:5 by , 12 years ago
Replying to sjoelund.se:
And my qwt was also 5.2.2... So... What did Adeel do? :)
(Also, were OMPlot and OMEdit compiled with gcc 4.4 or 4.7?)
I think it has nothing to do with OMPlot. Probably the problem is with Qt and here SimulationDialog.cpp:679. It could be that Qt doesn't set the status of the process to QProcess::NotRunning properly and the user always stays in the loop forever. I will see of we can use some other way to get out of this loop.
comment:6 by , 12 years ago
Btw it is working fine on Windows 7 and on my Linux Ubuntu 32 virtual box. So, i can't test it properly.
comment:7 by , 12 years ago
Replying to sjoelund.se:
And my qwt was also 5.2.2... So... What did Adeel do? :)
(Also, were OMPlot and OMEdit compiled with gcc 4.4 or 4.7?)
My OMEdit is compiled with gcc 4.4
follow-up: 9 comment:8 by , 12 years ago
I have added some code that will hopefully fix the problem. Update to r15773. Sorry I can't test it :).
follow-up: 10 comment:9 by , 12 years ago
follow-up: 11 comment:10 by , 12 years ago
Replying to pupala@…:
Replying to adeas31:
I have added some code that will hopefully fix the problem. Update to r15773. Sorry I can't test it :).
With gcc-4.4 recompiled OMEdit without change. I recompile entrire program with gcc-4.7
You mean you still have the same problem? If yes then I suggest changing the Qt version because Qt is not informing the application that the process is finished.
Can you check in your process monitor if the DCMotor executable is running or not?
comment:11 by , 12 years ago
I have still same problem. And after recompile with gcc-4.7 too.
You can write me, please, how to compile it on my system, so I can send to debian-qt maintainers as a mistake?
And where is a model of DC-motor?
I see only DC_PermanentMagnet, DC_ElectricalExcited, DC_SeriesExcited
Thank you
Rony
You mean you still have the same problem? If yes then I suggest changing the Qt version because Qt is not informing the application that the process is finished.
Can you check in your process monitor if the DCMotor executable is running or not?
follow-up: 13 comment:12 by , 12 years ago
He wants to know if there is a process epc4 still running on the system (ps axu | grep epc4).
follow-up: 14 comment:13 by , 12 years ago
No, not running.
OMEdit create these packages in /tmp/OpenModelica/OMEdit :
epc4.c
epc4_functions.c
epc4_functions.h
epc4_info.xml
epc4_init.xml
epc4.libs
epc4.log
epc4.makefile
epc4_model.h
epc4.o
epc4_prof.data
epc4_records.c
epc4_records.o
epc4_res.mat
omeditcommands.log
This is finished in 3 seconds, and OMEdit has no response, and only OMEdit ans omc process runing after this. OMEdit with 99% processor usage.
Rony
Replying to sjoelund.se:
He wants to know if there is a process epc4 still running on the system (ps axu | grep epc4).
follow-up: 15 comment:14 by , 12 years ago
OMEdit still create in /tmp/OpenModelica/OMEdit binary executable file epc4.
I forgot to add this.
Thank you
Rony
follow-up: 17 comment:15 by , 12 years ago
Replying to anonymous:
OMEdit still create in /tmp/OpenModelica/OMEdit binary executable file epc4.
I forgot to add this.
Thank you
Rony
Yes check when OMEdit is using 99% of CPU at that time any epc4 executable is running or not? You can check it in your process monitor or as Per suggested.
You need to download the OpenModelica sources and then check the readme files for instructions on how to compile.
https://www.openmodelica.org/index.php/developersresources/source-code
follow-up: 19 comment:16 by , 12 years ago
If you update to r15777 then you can run the application with
--debug=true
command line parameter. Please run the application with debug argument and send me the output produced by OMEdit while running the simulation.
follow-up: 18 comment:17 by , 12 years ago
After start simulation from OMEdit cpu usage jump to 99% with OMEdit, and OMEdit has no response. In /tmp/OpenModelica/OMEdit directory resulting files
epc4
epc4_functions.c
epc4_functions.h
epc4_info.xml
epc4_init.xml
epc4.libs
epc4.log
epc4.makefile
epc4_model.h
epc4.o
epc4_prof.data
epc4_records.c
epc4_records.o
epc4_res.mat
omeditcommands.log
After this, OMEdit still does not respond, and use 99% of cpu, and not usable. No other process running. Only omc, with 0,1% cpu usage. epc4 not running. Only OMEdit.
It seems that the simulation takes place, because arise epc4_res.mat file, which is loadable and usable in OMEdit.
I have openmodelica sources downloaded by svn and set up as described in the file README.Linux.txt, and rml+mmc also.
Rony
Replying to adeas31:
Replying to anonymous:
OMEdit still create in /tmp/OpenModelica/OMEdit binary executable file epc4.
I forgot to add this.
Thank you
Rony
Yes check when OMEdit is using 99% of CPU at that time any epc4 executable is running or not? You can check it in your process monitor or as Per suggested.
You need to download the OpenModelica sources and then check the readme files for instructions on how to compile.
https://www.openmodelica.org/index.php/developersresources/source-code
comment:18 by , 12 years ago
The generated files are correct.
Have you tried it with debug argument?
Run it like,
./OMEdit --debug=true
The OMEdit will print information on the console. I want to see that information.
Replying to pupala@…:
After start simulation from OMEdit cpu usage jump to 99% with OMEdit, and OMEdit has no response. In /tmp/OpenModelica/OMEdit directory resulting files
epc4
epc4_functions.c
epc4_functions.h
epc4_info.xml
epc4_init.xml
epc4.libs
epc4.log
epc4.makefile
epc4_model.h
epc4.o
epc4_prof.data
epc4_records.c
epc4_records.o
epc4_res.mat
omeditcommands.log
After this, OMEdit still does not respond, and use 99% of cpu, and not usable. No other process running. Only omc, with 0,1% cpu usage. epc4 not running. Only OMEdit.
It seems that the simulation takes place, because arise epc4_res.mat file, which is loadable and usable in OMEdit.
I have openmodelica sources downloaded by svn and set up as described in the file README.Linux.txt, and rml+mmc also.
Rony
Replying to adeas31:
Replying to anonymous:
OMEdit still create in /tmp/OpenModelica/OMEdit binary executable file epc4.
I forgot to add this.
Thank you
Rony
Yes check when OMEdit is using 99% of CPU at that time any epc4 executable is running or not? You can check it in your process monitor or as Per suggested.
You need to download the OpenModelica sources and then check the readme files for instructions on how to compile.
https://www.openmodelica.org/index.php/developersresources/source-code
by , 12 years ago
follow-up: 22 comment:19 by , 12 years ago
OMEDit --debug=true
rony@ntb1:~/openmodelica$ OMEdit --debug=true starting the simulation process started the simulation process running the simulation process running the simulation process running the simulation process running the simulation process running the simulation process running the simulation process simulationProcessFinished slot is called simulation process finished
cursor on new line, and OMEdit opening plot windows, and don't responding. Use 100% from cpu.
top
top - 13:13:51 up 5:50, 5 users, load average: 1,15, 1,12, 0,83 Tasks: 185 total, 3 running, 182 sleeping, 0 stopped, 0 zombie %Cpu(s): 52,4 us, 0,8 sy, 0,0 ni, 46,3 id, 0,3 wa, 0,0 hi, 0,2 si, 0,0 st KiB Mem: 4058844 total, 3701892 used, 356952 free, 80272 buffers KiB Swap: 10476540 total, 6328 used, 10470212 free, 1750492 cached PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 11656 rony 20 0 670m 163m 38m R 100,1 4,1 9:45.20 OMEdit 4858 rony 20 0 553m 43m 25m R 1,7 1,1 2:19.75 chromium 4147 rony 20 0 375m 27m 15m S 1,3 0,7 0:21.89 konsole 2655 root 20 0 157m 51m 18m S 1,0 1,3 5:40.45 Xorg 4482 rony 20 0 1158m 215m 23m S 0,7 5,4 2:05.88 chromium 2844 root 20 0 41392 1140 804 S 0,3 0,0 0:57.41 cpufreqd
ps aux output in attachment
epc4 not running
Rony
Replying to adeas31:
If you update to r15777 then you can run the application with
--debug=truecommand line parameter. Please run the application with debug argument and send me the output produced by OMEdit while running the simulation.
follow-up: 21 comment:20 by , 12 years ago
If Adeel cannot find anything else to suggest, GDB might be most helpful here:
gdb ./OMEdit
run
wait for OMEdit to spin
ctrl+c
bt
Post the functions on the stack. But given the fact this is Qt, odds are it won't tell us much.
comment:21 by , 12 years ago
Here
^C Program received signal SIGINT, Interrupt. 0x00007ffff4ae9fe0 in QWidgetPrivate::childAtRecursiveHelper(QPoint const&, bool, bool) const () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 (gdb) bt #0 0x00007ffff4ae9fe0 in QWidgetPrivate::childAtRecursiveHelper(QPoint const&, bool, bool) const () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #1 0x00007ffff4aea0d6 in QWidgetPrivate::childAtRecursiveHelper(QPoint const&, bool, bool) const () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #2 0x00007ffff4aea0d6 in QWidgetPrivate::childAtRecursiveHelper(QPoint const&, bool, bool) const () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #3 0x00007ffff4aea0d6 in QWidgetPrivate::childAtRecursiveHelper(QPoint const&, bool, bool) const () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #4 0x00007ffff4aea0d6 in QWidgetPrivate::childAtRecursiveHelper(QPoint const&, bool, bool) const () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #5 0x00007ffff4aea0d6 in QWidgetPrivate::childAtRecursiveHelper(QPoint const&, bool, bool) const () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #6 0x00007ffff4aea0d6 in QWidgetPrivate::childAtRecursiveHelper(QPoint const&, bool, bool) const () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #7 0x00007ffff4aea1e1 in QWidgetPrivate::childAt_helper(QPoint const&, bool) const () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #8 0x00007ffff4aab931 in QApplicationPrivate::sendSyntheticEnterLeave(QWidget*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #9 0x00007ffff4afc492 in QWidget::setVisible(bool) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #10 0x00007ffff4f23a02 in QAbstractScrollAreaPrivate::layoutChildren() () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #11 0x00007ffff424aa2e in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #12 0x00007ffff4af969a in QWidget::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #13 0x00007ffff4ea4d36 in QFrame::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #14 0x00007ffff4f2497b in QAbstractScrollArea::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #15 0x00007ffff4eccedd in QMdiArea::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #16 0x00007ffff4aaa70c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #17 0x00007ffff4aaeb8a in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #18 0x00007ffff4235b5e in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #19 0x00007ffff42399e1 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #20 0x00007ffff42640e3 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #21 0x00007ffff1c24355 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #22 0x00007ffff1c24688 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #23 0x00007ffff1c24744 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #24 0x00007ffff4264276 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #25 0x00007ffff4b4b83e in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #26 0x00007ffff42348af in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #27 0x00007ffff4234b38 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #28 0x00007ffff4239cf8 in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #29 0x0000000000433256 in main ()
follow-up: 23 comment:22 by , 12 years ago
Thanks Rony. The output is correct. So the error is not what I was thinking. I added some more debug information in r15779. Can you please try again and post the output? You should get this if everything goes fine,
starting the simulation process started the simulation process running the simulation process running the simulation process running the simulation process running the simulation process running the simulation process running the simulation process simulationProcessFinished slot is called simulation process finished readSimulationResultVars closeSimulationResultFile switchToPlottingView addPlotVariablestoTree show variables widget
What do you mean by "OMEdit opening plot windows"? It should switch to plotting perspective and should only open up one plot window.
Replying to pupala@…:
OMEDit --debug=true
rony@ntb1:~/openmodelica$ OMEdit --debug=true starting the simulation process started the simulation process running the simulation process running the simulation process running the simulation process running the simulation process running the simulation process running the simulation process simulationProcessFinished slot is called simulation process finishedcursor on new line, and OMEdit opening plot windows, and don't responding. Use 100% from cpu.
top
top - 13:13:51 up 5:50, 5 users, load average: 1,15, 1,12, 0,83 Tasks: 185 total, 3 running, 182 sleeping, 0 stopped, 0 zombie %Cpu(s): 52,4 us, 0,8 sy, 0,0 ni, 46,3 id, 0,3 wa, 0,0 hi, 0,2 si, 0,0 st KiB Mem: 4058844 total, 3701892 used, 356952 free, 80272 buffers KiB Swap: 10476540 total, 6328 used, 10470212 free, 1750492 cached PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 11656 rony 20 0 670m 163m 38m R 100,1 4,1 9:45.20 OMEdit 4858 rony 20 0 553m 43m 25m R 1,7 1,1 2:19.75 chromium 4147 rony 20 0 375m 27m 15m S 1,3 0,7 0:21.89 konsole 2655 root 20 0 157m 51m 18m S 1,0 1,3 5:40.45 Xorg 4482 rony 20 0 1158m 215m 23m S 0,7 5,4 2:05.88 chromium 2844 root 20 0 41392 1140 804 S 0,3 0,0 0:57.41 cpufreqdps aux output in attachment
epc4 not running
Rony
Replying to adeas31:
If you update to r15777 then you can run the application with
--debug=truecommand line parameter. Please run the application with debug argument and send me the output produced by OMEdit while running the simulation.
follow-up: 24 comment:23 by , 12 years ago
OMEdit --debug=true on r15781
rony@ntb1:~/openmodelica$ OMEdit --debug=true starting the simulation process started the simulation process running the simulation process running the simulation process running the simulation process running the simulation process running the simulation process running the simulation process simulationProcessFinished slot is called simulation process finished readSimulationResultVars closeSimulationResultFile switchToPlottingView addPlotVariablestoTree show variables widget
...and same problem
Rony
follow-up: 25 comment:24 by , 12 years ago
And here is gdb output on r15781
^C Program received signal SIGINT, Interrupt. 0x00007ffff4aaa3f2 in QApplication::compressEvent(QEvent*, QObject*, QPostEventList*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 (gdb) bt #0 0x00007ffff4aaa3f2 in QApplication::compressEvent(QEvent*, QObject*, QPostEventList*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #1 0x00007ffff4239363 in QCoreApplication::postEvent(QObject*, QEvent*, int) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #2 0x00007ffff4afc746 in QWidget::setVisible(bool) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #3 0x00007ffff4f23a02 in QAbstractScrollAreaPrivate::layoutChildren() () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #4 0x00007ffff424aa2e in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #5 0x00007ffff4af969a in QWidget::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #6 0x00007ffff4ea4d36 in QFrame::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #7 0x00007ffff4f2497b in QAbstractScrollArea::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #8 0x00007ffff4eccedd in QMdiArea::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #9 0x00007ffff4aaa70c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #10 0x00007ffff4aaeb8a in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #11 0x00007ffff4235b5e in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #12 0x00007ffff42399e1 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #13 0x00007ffff42640e3 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #14 0x00007ffff1c24355 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #15 0x00007ffff1c24688 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x00007ffff1c24744 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #17 0x00007ffff4264276 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #18 0x00007ffff4b4b83e in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #19 0x00007ffff42348af in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #20 0x00007ffff4234b38 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #21 0x00007ffff4239cf8 in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #22 0x000000000043324d in main () (gdb)
Rony
comment:25 by , 12 years ago
I can report this to a Debian QT/KDE maintainers as en error in QT library package in Wheezy?
And what to send them? Outputs from the debugger?
Rony
comment:26 by , 12 years ago
I think Adeel should try to fix this. But he's going on vacation for roughly a month (he will get bored and do some work; but we do not know when he checks in). His trace shows that the program does progress further than he thought. So the bug should be in OMEdit somewhere.
comment:27 by , 12 years ago
I the same OMEdit bug occurs on Debian wheezy.
My testcase is
Modelica->Mechanics->Rotational->Examples-First
After simulating the model, OMEdit consumes 100% CPU
and becomes unusable.
I installed the modelica packages from:
http://build.openmodelica.org/apt wheezy nightly
Following some of your ideas above, I tried the following steps:
on wheezy QT library are of version 4:4.8.2
my first step was to upgrade to QT library version 4:4.8.4
(from debian/experimental).
-> no success
OMEdit uses libqwt5-qt4 ( 5.2.2-3 )
ldd /usr/bin/OMEdit | grep -i -e qw -e qt
libqwt-qt4.so.5 => /usr/lib/libqwt-qt4.so.5 (0xb754d000)
libQtWebKit.so.4 => /usr/lib/i386-linux-gnu/libQtWebKit.so.4 (0xb5e02000)
libQtSvg.so.4 => /usr/lib/i386-linux-gnu/libQtSvg.so.4 (0xb5dab000)
libQtXml.so.4 => /usr/lib/i386-linux-gnu/libQtXml.so.4 (0xb5d69000)
libQtGui.so.4 => /usr/lib/i386-linux-gnu/libQtGui.so.4 (0xb5285000)
libQtNetwork.so.4 => /usr/lib/i386-linux-gnu/libQtNetwork.so.4 (0xb513e000)
libQtCore.so.4 => /usr/lib/i386-linux-gnu/libQtCore.so.4 (0xb4e4f000)
to test with libqwt6, I compiled from SVN (15982)
ldd build/bin/OMEdit | grep -i -e qw -e qt
libqwt.so.6 => /usr/lib/libqwt.so.6 (0xb7519000)
libQtWebKit.so.4 => /usr/lib/i386-linux-gnu/libQtWebKit.so.4 (0xb5dce000)
libQtSvg.so.4 => /usr/lib/i386-linux-gnu/libQtSvg.so.4 (0xb5d77000)
libQtXml.so.4 => /usr/lib/i386-linux-gnu/libQtXml.so.4 (0xb5d35000)
libQtGui.so.4 => /usr/lib/i386-linux-gnu/libQtGui.so.4 (0xb5251000)
libQtNetwork.so.4 => /usr/lib/i386-linux-gnu/libQtNetwork.so.4 (0xb510a000)
libQtCore.so.4 => /usr/lib/i386-linux-gnu/libQtCore.so.4 (0xb4e1b000)
dpkg -l "libqwt6"
=> version: 6.0.0-1.2
no success !!
for me this indicates that Qt seems not to be the reason for this bug.
If I have time I will try profiling with valgrind as a next step.
Anyway I hope this information will help to improve this great project.
comment:30 by , 11 years ago
| Resolution: | → worksforme |
|---|---|
| Status: | new → closed |
A lot has been changed in the way simulation runs and plotting is done. So, I am wondering if this bug is still valid or not.
However, I am closing it as works for me. If the bug is still valid please provide a error log using the latest nightly build and feel free to reopen it.
I just compared the versions of libqt4 and libqwt to Ubuntu 12.10. Qwt is the same, qt4 is 4.6 vs. 4.8. So maybe it's a Qt 4.8 issue? I think Per has 4.8 in arch linux so he could have a look and see if the model is problematic.
Do all models hang or just this one (it does not hang on Ubuntu).