Opened 7 years ago

Closed 5 years ago

#39402 closed defect (worksforme)

qtiplot crashes - qt4-mac related

Reported by: juresco@… Owned by: NicosPavlov
Priority: Normal Milestone:
Component: ports Version: 2.1.3
Keywords: Cc: michaelld (Michael Dickens)
Port: qtiplot

Description (last modified by larryv (Lawrence Velázquez))


I have experienced again systematical crashes of qtiplot, configuration: qt4-mac @4.8.4, and qtiplot @

About one year ago, I posted a ticket with the same problem. After upgrading to qt4-mac 4.8.0 the problem has seemed to be solved, but now it appears again in the same conditions described in my previous ticket (see comment:8:ticket:33323)

Change History (4)

comment:1 Changed 7 years ago by larryv (Lawrence Velázquez)

Cc: michaelld@… added
Description: modified (diff)
Owner: changed from macports-tickets@… to nicos@…
Port: qtiplot added

Wow, please do not paste so much text into ticket descriptions or comments. Submit the crash log as an attachment to this ticket.

And Cc relevant port maintainers in future tickets.

comment:2 Changed 7 years ago by michaelld (Michael Dickens)

I just did "sudo port install qtiplot +python27 +qtexengine", which succeeded the 2nd try (I did not check out the first try to see). I then launch the app and it works for me. What do I need to do to replicate your issue?

comment:3 Changed 7 years ago by juresco@…

Hello, The application works fine for me too, but only if no CPU intensive application is running simultaneously. For example try to perform a long compilation or run some simulation (in my case the crashes occur when I'm running fortran simulations from terminal), then try to load data in qtiplot and use it, you will see the application freezes or stops responding and then crashes. There is some problem with memory allocation/ seems like a bottleneck ...

comment:4 Changed 5 years ago by michaelld (Michael Dickens)

Resolution: worksforme
Status: newclosed

Guessing this is no longer a real issue, and it did work for me at the time. So, I'm closing this ticket. If this is still an issue, then please reopen & provide more information.

Note: See TracTickets for help on using tickets.