Ticket #25956 (closed defect: worksforme)
xfig 3.2.5 crashes when accessing the menu multiple times
| Reported by: | lawrence.ong@… | Owned by: | macports-tickets@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 1.9.1 |
| Keywords: | Cc: | ||
| Port: | xfig |
Description (last modified by jmr@…) (diff)
When the menu is accessed multiple times, the program crashes.
Steps to Reproduce:
- Draw some figure and save it as 1.fig
- Modify the figure and save it as 2.fig
- Open 1.fig, and export it as eps
- Open 2.fig, and export it as eps
- Keep repeating 3 and 4, the program will crash at some point.
I tried to recompile the xfig without XAW3D, but the problem persists. Both version 3.2.5 and 3.2.5b have this problems.
I don't encounter this problem, however, in Linux.
Change History
comment:1 Changed 3 years ago by jmr@…
- Priority changed from High to Normal
- Description modified (diff)
- Port changed from xfig 3.2.5 to xfig
comment:2 Changed 3 years ago by lawrence.ong@…
I got this error message in Terminal. Not sure if it helps:
X error trapped - error message follows: BadMatch (invalid parameter attributes) Request code: X_GetWindowAttributes xfig: figure empty or not modified - exiting
comment:3 Changed 3 years ago by ryandesign@…
Please remember to use WikiFormatting and to preview before submitting so you can verify your formatting is correct.
I just updated xfig in MacPorts to version 3.2.5b. Please try that version. (I assume you had built xfig 3.2.5b manually before?) If that still doesn't work, have you already reported your findings to the developers of xfig? That would probably be a good idea so they can fix this in their software.
comment:4 Changed 3 years ago by lawrence.ong@…
The problem still persists in the latest version 3.2.5b.
I have reported this problem to XQuartz. I tried to run xfig tunneled from a Linux machine (with xfig installed) via "ssh -X", and I still ran into this problem. The problem does not occur locally on the Linux machine though. So, I suspect that it might be some problem with Mac's implementation of X11.

