This forum is archived, go to the new forum!

This is the old fritzing discussion forum. Search it for valuable information from 2009 to 2015.

0.9.0 now extremely unresponsive / osx 10.9.4

mxmx2000 4 years, 8 months ago

hi,

 

glad to see there was an update. it's not at all working for me though -- fritzing is now very slow and unresponsive to user interaction: so unresponsive as to be unusable, both when i start a project from scratch or edit an existing one. i can't properly select parts on the pcb view, connecting parts doesn't work properly, neither does zooming in/out etc. 

 

fwiw i'm on 10.9.4, mac book pro.

André Knörig 4 years, 8 months ago

André Knörig

Hi, the exact opposite is what should happen.. We made the Qt5 upgrade mostly because of the noticeable performance improvement under OSX. We are running it on several 10.9 machines, though I'm on 10.9.2. I will update to 10.9.4 today, but I assume that won't have an effect.

Are you sure it's not related to anything else? Did you do a clean install, and a reboot of the machine?

mxmx2000 4 years, 8 months ago

hi andré --

 

thanks for replying. i did reboot my machine, but no, no clean install. i just hit replace existing. i'll give it another try but i guess i'll have to export all my custom parts first then.

 

M

 

 

André Knörig 4 years, 8 months ago

André Knörig

Hi M, I now updated to 10.9.4 and I don't see any differences.

Your personal settings, including custom parts, are in /Users/<username>/.config/Fritzing. You can make a backup copy of those, before you delete them.

Maybe also just try another re-install, it could have been that the download or unzipping did not properly complete. I also briefly searched on Qt, but there aren't any reports about an unresponsive Qt5.

Vlad 4 years, 8 months ago

I installed today for the first time Fritzing v0.9 on an iMac running Mavericks 10.9.4 - and it crashes all the time (for example almost every time when I change the attributes of an object - eg. color of a wire).

The auto-wiring function does not deliver the proper result (>60% of the wires not solved). Something basic seem not to work here. Therefore, I have no fun so far working with it. :-/

Fabian Althaus 4 years, 8 months ago

hej vlad, that's really not good. could you please give us the trace-back that comes up when the application crashes. we do not have this bug on our maverick machines and need more information about the crash on your machine.

Vlad 4 years, 8 months ago

sure, Fa, how to send it to you?

Vlad 4 years, 8 months ago

sure, Fa, how to send it to you?

Vlad 4 years, 8 months ago

sure, Fa, how to send it to you?

Vlad 4 years, 8 months ago

sure, Fa, how to send it to you?

Vlad 4 years, 8 months ago

sure, Fa, how to send it to you?

Fabian Althaus 4 years, 8 months ago

hej vlad,

please write an email to support (at) fritzing (dot) org

Vlad 4 years, 8 months ago

DONE!

Fabian Althaus 4 years, 8 months ago

hej Vlad, 

please send the report again to my own email-adress because the support system does not get the mail 

till now. sorry for the problems :)

fabian (at) fritzing (dot) org

Vlad 4 years, 7 months ago

done!

André Knörig 4 years, 7 months ago

André Knörig

Hi Vlad, Thanks for sending your crash report. I'm copying the interesting snippet here below.

It seems to crash on "processTabletEvent", which suggests that you are using a Tablet to interact with the application?

I found a note about a similar issue here: https://bugreports.qt-project.org/browse/QTBUG-35984

This one seems to be fixed in Qt 5.3. Unfortunately there are other issues in 5.3 that haven't been fixed yet, so we cannot upgrade. But it should work if you unplug your tablet?

 

 

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   QtWidgets                     0x0000000100b990aa QWidget::mapFromGlobal(QPoint const&) const + 58
1   QtWidgets                     0x0000000100b9dbc6 0x100b1a000 + 539590
2   QtWidgets                     0x0000000100b9b4a1 0x100b1a000 + 529569
3   QtWidgets                     0x0000000100b45f2c QApplicationPrivate::notify_helper(QObject*, QEvent*) + 300
4   QtWidgets                     0x0000000100b48a1d QApplication::notify(QObject*, QEvent*) + 6157
5   org.fritzing.Fritzing         0x000000010003a6fd FApplication::notify(QObject*, QEvent*) + 29
6   QtCore                         0x00000001017470b2 QCoreApplication::notifyInternal(QObject*, QEvent*) + 114
7   QtGui                         0x000000010111985f QGuiApplicationPrivate::processTabletEvent(QWindowSystemInterfacePrivate::TabletEvent*) + 911
8   QtGui                         0x0000000101115630 QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) + 944
9   QtGui                         0x0000000101105338 QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 136
10  libqcocoa.dylib               0x00000001032dd4c7 0x1032c3000 + 107719
11  libqcocoa.dylib               0x00000001032ddfd8 0x1032c3000 + 110552
12  com.apple.CoreFoundation       0x00007fff952185b1 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
13  com.apple.CoreFoundation       0x00007fff95209c62 __CFRunLoopDoSources0 + 242
14  com.apple.CoreFoundation       0x00007fff952093ef __CFRunLoopRun + 831
15  com.apple.CoreFoundation       0x00007fff95208e75 CFRunLoopRunSpecific + 309
16  com.apple.HIToolbox           0x00007fff97f8ea0d RunCurrentEventLoopInMode + 226
17  com.apple.HIToolbox           0x00007fff97f8e685 ReceiveNextEventCommon + 173
18  com.apple.HIToolbox           0x00007fff97f8e5bc _BlockUntilNextEventMatchingListInModeWithFilter + 65
19  com.apple.AppKit               0x00007fff8f2db24e _DPSNextEvent + 1434
20  com.apple.AppKit               0x00007fff8f2da89b -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 122
21  com.apple.AppKit               0x00007fff8f2ce99c -[NSApplication run] + 553
22  libqcocoa.dylib               0x00000001032dcd44 0x1032c3000 + 105796
23  QtCore                         0x000000010174464d QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 397
24  QtCore                         0x0000000101747652 QCoreApplication::exec() + 354
25  org.fritzing.Fritzing         0x000000010004e1b4 main + 340
26  org.fritzing.Fritzing         0x0000000100005e94 start + 52

Vlad 4 years, 7 months ago

Hello, André,

Yes, I use indeed a Wacom Bamboo tablet. I will try with a mouse instead, however, I hope that the fix for the tablet will come soon.

Thanks again for your help,

Vlad

Vlad 4 years, 7 months ago

Hello, André,

I made some tests using the mouse - and it seem to work well. I am not a programmer and I do not understand what qt-project is... so, what should I do regarding the Wacom Board (besides selling it on Ebay)?

Regards,

Vlad 

André Knörig 4 years, 7 months ago

André Knörig

Well, there isn't much you can do for now. It's not Wacom's fault, rather that of Qt. Just remember to not use the Tablet when working with Fritzing. It might already be fixed in our next release.

mxmx2000 4 years, 7 months ago

further re this (apparently my) problem with 10.9.4 / fritzing 0.9. i have no clue what might be going on, but the problem persists. i've reinstalled a few times, and at one point it actually worked (indeed much smoother). next time i start up fritzing, same thing again. i enter the pcb view (blank project) and the cpu shoots up to 100% ... 

 

for the time being, i downgraded to the last 0.8.x version, which is running fine.