-
Notifications
You must be signed in to change notification settings - Fork 842
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Application freezes and crashes #3084
Comments
I'm afraid that's due to the relatively naive implementation we made. It's probably not freezing, but just taking a lot of time to compute the stripboard behaviour. More optimization work is needed here. |
This behavior is caused by #3090 (see there for a workaround). It is unrelated to the selected component. Verified with 0.9.2b on Linux. |
==No. 2======= ==No. 1======= When I run fritzing as the administrator, it does not freeze at the start but do after I do some operations like the ones mentioned by @spelare69 . PC Lenovo 20KFA01PCD laptop |
Gemba is right: Because of #3090 all connectors of the board are connected to each other. This is not a typical case for a stripboard, and should be avoided. Furthermore, when Fritzing tries to build a list of connected items, it uses said naive implementation. |
…ritzing#2998 and fritzing#3084. The slow performance is still present but the extended area is not shortcircuited.
When starting a new design and the steps below are followed the application freezes and stops responding.
As long as Component is not draged on top of the stripboard there is no problem.
This freezing is the same every time and I have tried 7-8 times.
No problem with smaller stripboard (default setting 30 columns x 20 rows) but when changing smaller stripboard design size to size 39 columns x 30 rows the application frezzes and stops responding.
Computer system:
windows 7 32-bit with service pack 1
i5 - 4670 3.40 GHz, 4GB of RAM
BR
Spelare69
The text was updated successfully, but these errors were encountered: