You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Been having issues in general with pyfa in regards to the new MacOS. Similarly this build is giving the same crashes.
Just random crashes that tend to happen whenever pyfa is open, I can be changing something, just have it open, it occurs after seconds, or minutes of using it. Truly random crashes.
Full reported error & system configuration is below:
No worries, I tried to build it locally since the bug was annoying me but somehow could never get my MacOS to compile the wxPython with the exact version of the requirements.txt.
Going off the latest stable wxPython version by just removing the exact version from the requirements.txt file seems to cause a different set of errors which lead to pyfa not being able to boot properly.
If you need a guinea pig with MacOS for your builds, I'll happily have a go on my machine to test building it.
v2.36 is still crashing for me on Big Sur 11.4. The crash seems random and does not replicate under the same actions. Sometimes a particular action will cause a crash, sometimes it won't. But, it consistently crashes within a couple minutes of working with a fit. Here's the first section of the crash report:
In an effort to try to help debug the problems with the OSX implementation, I crashed Pyfa v2.37 dev1 multiple times and then analyzed the crash reports to see see if there were any common elements that might point to the cause.
In all cases, the same error was reported:
...triggered by the same sequence:
In every case the contents of four registers were identical, r12, r14, rip, and rfl:
I have no idea what any of this means -- my knowledge of programming doesn't extend much beyond print("hello world")-- but, I thought this information might help actually competent people get closer to figuring out the source of the problem.
In an effort to try to help debug the problems with the OSX implementation, I crashed Pyfa v2.37 dev1 multiple times and then analyzed the crash reports to see see if there were any common elements that might point to the cause.
In all cases, the same error was reported:
...triggered by the same sequence:
In every case the contents of four registers were identical, r12, r14, rip, and rfl:
I have no idea what any of this means -- my knowledge of programming doesn't extend much beyond print("hello world")-- but, I thought this information might help actually competent people get closer to figuring out the source of the problem.
I am not sure I have seen this particular crash (judging by the stacktrace). You can try my fix (https://github.com/philipbel/Pyfa) from PR #2346, which I have been running successfully for a few weeks now without any issues.
I have been having the same error and constant crashes to the point where it's almost unusable.
I'm still having the same issue as well. I'm not one of the devs, but as I understand it, @philipbel figured out that there is a problem with the way one of the underlying third-party libraries/toolkits interact with Retina Macs rather than a problem with Pyfa itself. Fixing it requires migrating to a new version, but doing so will have broader impacts that require require testing and potentially modifications to the code. I think the devs are working on it, but it's going to take some time. In the meantime, @philipbel has a fix that you can run as a local build (https://github.com/philipbel/Pyfa). I don't know how to run a local build, but if you do, you might give it a try.
In an effort to try to help debug the problems with the OSX implementation, I crashed Pyfa v2.37 dev1 multiple times and then analyzed the crash reports to see see if there were any common elements that might point to the cause. In all cases, the same error was reported: ...triggered by the same sequence: In every case the contents of four registers were identical, r12, r14, rip, and rfl:
I have no idea what any of this means -- my knowledge of programming doesn't extend much beyond print("hello world")-- but, I thought this information might help actually competent people get closer to figuring out the source of the problem.
I am not sure I have seen this particular crash (judging by the stacktrace). You can try my fix (https://github.com/philipbel/Pyfa) from PR #2346, which I have been running successfully for a few weeks now without any issues.
@philipbel I know this is elementary, but as I mentioned in my comment above, I've never tried your fix because I don't know how to do a local build. Are there any references you can point me to that would assist in rectifying my fundamental ignorance of this topic?
In an effort to try to help debug the problems with the OSX implementation, I crashed Pyfa v2.37 dev1 multiple times and then analyzed the crash reports to see see if there were any common elements that might point to the cause. In all cases, the same error was reported: ...triggered by the same sequence: In every case the contents of four registers were identical, r12, r14, rip, and rfl:
I have no idea what any of this means -- my knowledge of programming doesn't extend much beyond print("hello world")-- but, I thought this information might help actually competent people get closer to figuring out the source of the problem.
I am not sure I have seen this particular crash (judging by the stacktrace). You can try my fix (https://github.com/philipbel/Pyfa) from PR #2346, which I have been running successfully for a few weeks now without any issues.
@philipbel I know this is elementary, but as I mentioned in my comment above, I've never tried your fix because I don't know how to do a local build. Are there any references you can point me to that would assist in rectifying my fundamental ignorance of this topic?
Follow the instructions from https://github.com/pyfa-org/Pyfa/blob/master/CONTRIBUTING.md on how to prepare the data. The only caveat is that a venv environment didn't work for me, so I use a conda virtual environment (install miniconda via Homebrew and create a new environment for Pyfa). So, instead of python -m venv PyfaEnv , you have to do conda create -p ~/.conda/envs/pyfa python=3.8, followed by conda activate ~/.conda/envs/pyfa.
Install python.app for pythonw to be available (conda install python.app).
Run pythonw pyfa.py from within the conda environment to run the local version of Pyfa.
In an effort to try to help debug the problems with the OSX implementation, I crashed Pyfa v2.37 dev1 multiple times and then analyzed the crash reports to see see if there were any common elements that might point to the cause. In all cases, the same error was reported: ...triggered by the same sequence: In every case the contents of four registers were identical, r12, r14, rip, and rfl:
I have no idea what any of this means -- my knowledge of programming doesn't extend much beyond print("hello world")-- but, I thought this information might help actually competent people get closer to figuring out the source of the problem.
I am not sure I have seen this particular crash (judging by the stacktrace). You can try my fix (https://github.com/philipbel/Pyfa) from PR #2346, which I have been running successfully for a few weeks now without any issues.
@philipbel I know this is elementary, but as I mentioned in my comment above, I've never tried your fix because I don't know how to do a local build. Are there any references you can point me to that would assist in rectifying my fundamental ignorance of this topic?
1. Clone my fork from https://github.com/philipbel/Pyfa
2. Follow the instructions from https://github.com/pyfa-org/Pyfa/blob/master/CONTRIBUTING.md on how to prepare the data. The only caveat is that a `venv` environment didn't work for me, so I use a conda virtual environment (install `miniconda` via Homebrew and create a new environment for Pyfa). So, instead of `python -m venv PyfaEnv `, you have to do `conda create -p ~/.conda/envs/pyfa python=3.8`, followed by `conda activate ~/.conda/envs/pyfa`.
3. Install `python.app` for `pythonw` to be available (`conda install python.app`).
4. Run `pythonw pyfa.py` from within the conda environment to run the local version of Pyfa.
once build this way, does it create a 'executable' file somewhere or do I have to keep running it from the conda environment?
Hey guys. Is there any progress on getting Pyfa working again on OSX? With a new native Eve client rolling out, the Mac user base is growing and Pyfa is such an essential for proper theory-crafting. Mac users like me really miss being able to use it. Really appreciate all your hard work making this incredible tool.
Activity
mathieudevos commentedon Jun 16, 2021
Hey,
Been having issues in general with pyfa in regards to the new MacOS. Similarly this build is giving the same crashes.
Just random crashes that tend to happen whenever pyfa is open, I can be changing something, just have it open, it occurs after seconds, or minutes of using it. Truly random crashes.
Full reported error & system configuration is below:
DarkFenX commentedon Jun 17, 2021
I will try updating dependencies to see if it helps, but won't have time until end of june
mathieudevos commentedon Jun 17, 2021
No worries, I tried to build it locally since the bug was annoying me but somehow could never get my MacOS to compile the wxPython with the exact version of the
requirements.txt.Going off the latest stable wxPython version by just removing the exact version from the
requirements.txtfile seems to cause a different set of errors which lead to pyfa not being able to boot properly.If you need a guinea pig with MacOS for your builds, I'll happily have a go on my machine to test building it.
philipbel commentedon Jun 19, 2021
@mathieudevos's crash is the same issue as #2304
philipbel commentedon Jun 20, 2021
I have (an attempt for) a fix for the macOS crash in PR #2346.
mathieudevos commentedon Jun 21, 2021
Built this on my own macbook with Python 3.9.1, currently testing, will let you know if it runs stable without crashing.
Any idea to force these crashes?
philipbel commentedon Jun 21, 2021
@mathieudevos for me it was almost immediately 8 out of 10 times or within a few minutes.
The issue in my PR is related to the images in the ship browser (left-hand side).
MauroCL-Developer commentedon Jun 28, 2021
Is v2.3.6 Big Sur ready? I have the question because still crashes as @philipbel described. If not, then I believe fixing works are on the pipe.
philipbel commentedon Jun 30, 2021
2.3.6 doesn't include my fix.
I have kept Pyfa running for a few days now, using it every now and then, and haven't seen the crash.
OrthelT commentedon Jul 1, 2021
v2.36 is still crashing for me on Big Sur 11.4. The crash seems random and does not replicate under the same actions. Sometimes a particular action will cause a crash, sometimes it won't. But, it consistently crashes within a couple minutes of working with a fit. Here's the first section of the crash report:
Process: pyfa [1058]
Path: /Applications/pyfa2.36.0a.app/Contents/MacOS/pyfa
Identifier: org.pyfaorg.pyfa
Version: 0.0.0 (???)
Code Type: X86-64 (Native)
Parent Process: ??? [1055]
User ID: 501
Date/Time: 2021-07-01 12:41:23.062 -0400
OS Version: macOS 11.4 (20F71)
Report Version: 12
Bridge OS Version: 5.4 (18P4663)
Anonymous UUID: 513184D1-2549-E403-3747-1B5D2E0BD30C
Time Awake Since Boot: 350 seconds
System Integrity Protection: enabled
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x000000014cfbb000
Exception Note: EXC_CORPSE_NOTIFY
Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [1058]
VM Regions Near 0x14cfbb000:
CoreAnimation 14cf84000-14cfbb000 [ 220K] rw-/rwx SM=ZER
-->
CoreAnimation 14cfc1000-14d151000 [ 1600K] rw-/rwx SM=PRV
OrthelT commentedon Jul 10, 2021
In an effort to try to help debug the problems with the OSX implementation, I crashed Pyfa v2.37 dev1 multiple times and then analyzed the crash reports to see see if there were any common elements that might point to the cause.
In all cases, the same error was reported:
...triggered by the same sequence:
In every case the contents of four registers were identical, r12, r14, rip, and rfl:
I have no idea what any of this means -- my knowledge of programming doesn't extend much beyond print("hello world")-- but, I thought this information might help actually competent people get closer to figuring out the source of the problem.
philipbel commentedon Jul 11, 2021
I am not sure I have seen this particular crash (judging by the stacktrace). You can try my fix (https://github.com/philipbel/Pyfa) from PR #2346, which I have been running successfully for a few weeks now without any issues.
Meghdeep commentedon Aug 9, 2021
I have been having the same error and constant crashes to the point where it's almost unusable.
OrthelT commentedon Aug 17, 2021
I'm still having the same issue as well. I'm not one of the devs, but as I understand it, @philipbel figured out that there is a problem with the way one of the underlying third-party libraries/toolkits interact with Retina Macs rather than a problem with Pyfa itself. Fixing it requires migrating to a new version, but doing so will have broader impacts that require require testing and potentially modifications to the code. I think the devs are working on it, but it's going to take some time. In the meantime, @philipbel has a fix that you can run as a local build (https://github.com/philipbel/Pyfa). I don't know how to run a local build, but if you do, you might give it a try.
OrthelT commentedon Aug 17, 2021
@philipbel I know this is elementary, but as I mentioned in my comment above, I've never tried your fix because I don't know how to do a local build. Are there any references you can point me to that would assist in rectifying my fundamental ignorance of this topic?
philipbel commentedon Aug 19, 2021
Hi, @OrthelT .
venvenvironment didn't work for me, so I use a conda virtual environment (installminicondavia Homebrew and create a new environment for Pyfa). So, instead ofpython -m venv PyfaEnv, you have to doconda create -p ~/.conda/envs/pyfa python=3.8, followed byconda activate ~/.conda/envs/pyfa.python.appforpythonwto be available (conda install python.app).pythonw pyfa.pyfrom within the conda environment to run the local version of Pyfa.LadyVanilla commentedon Aug 30, 2021
once build this way, does it create a 'executable' file somewhere or do I have to keep running it from the conda environment?
OrthelT commentedon Oct 13, 2021
Hey guys. Is there any progress on getting Pyfa working again on OSX? With a new native Eve client rolling out, the Mac user base is growing and Pyfa is such an essential for proper theory-crafting. Mac users like me really miss being able to use it. Really appreciate all your hard work making this incredible tool.