Opened 8 years ago

Closed 5 years ago

#1234 closed defect (fixed)

wxnviz - cause a gui crash

Reported by: epifanio Owned by: grass-dev@…
Priority: critical Milestone: 6.5.0
Component: wxGUI Version: svn-develbranch6
Keywords: nviz Cc:
CPU: OSX/Intel Platform: MacOSX

Description

Hi,

using grass65 on osx, in the mapdisplay wuindow if i select the 3dview combobox give me a gui crash and i have to restart the wxpython gui.

if wxnviz is not ready, why don-t disable it from the combo box (like for the digitizer)

Attachments (1)

WinGrass7_wxnviz_10122010_005720a.png (140.7 KB) - added by hellik 8 years ago.
wxnviz-python-crash

Download all attachments as: .zip

Change History (18)

comment:1 Changed 8 years ago by martinl

Milestone: 6.4.1

comment:2 Changed 8 years ago by cmbarton

The 3D visualizer is disabled in the stable GRASS 6.4.0 version.

GRASS 6.5 is an active development version. Because of this, somethings may not work or cause crashes. This is the nature of a dev version, although GRASS dev versions are pretty solid.

I'm using GRASS 6.5 and 7 actively on Mac OSX and have not experienced a crash in the viewer. Can you detail what caused it so that we can work on improving it?

There is a bug in which quitting the 3D viewer BEFORE switching the GIS manager window back to the layer-manager pane will cause the 3D controls to overlay the layer manager and lock them up. I don't know whether this is what you are experiencing, but I've submitted a fix to this for GRASS 7 and am waiting on testing results before backporting to 6.5

Michael

comment:3 Changed 8 years ago by epifanio

CPU: UnspecifiedOSX/Intel
Milestone: 6.4.16.5.0

Hi, yes i know is a devel branch,

mine is tiket is to report a problem i had ... if for you works, maybe it's probable a problem related to my system settings.

(btw on grass70 wx nviz "works", at least i'm able to moove the camera around a digital terrain model)

on 65 instead, when i try to use the "combo box" to select the 3d View .. the gui simple quit without any log.

i recorded a simple video to show the crash (5mb) i can't upload it until tomorrow on my ftp.

comment:4 in reply to:  2 Changed 8 years ago by hellik

Replying to cmbarton: [...]

There is a bug in which quitting the 3D viewer BEFORE switching the GIS manager window back to the layer-manager pane will cause the 3D controls to overlay the layer manager and lock them up. I don't know whether this is what you are experiencing, but I've submitted a fix to this for GRASS 7 and am waiting on testing results before backporting to 6.5

tested with the latest nightly-build of WinGrass7. switching back to 2d-view is possible without an overlay of the 3d controls.

but if I exit the wxgui, python is crashing. this doesn't occur if the wxgui is always only in 2d-view mode.

best regards Helmut

comment:5 Changed 8 years ago by martinl

Keywords: nviz added

comment:6 Changed 8 years ago by cmbarton

When I exit the GUI after being in 3D mode, I get error messages sent to the terminal. This is not a crash. And I don't know if the error messages are bogus or not, since they seem to have no effect on the operation of the program otherwise. Is this what you are talking about?

Michael

Changed 8 years ago by hellik

wxnviz-python-crash

comment:7 in reply to:  6 Changed 8 years ago by hellik

Replying to cmbarton:

When I exit the GUI after being in 3D mode, I get error messages sent to the terminal. This is not a crash. And I don't know if the error messages are bogus or not, since they seem to have no effect on the operation of the program otherwise. Is this what you are talking about?

no, the wxgui-grass-layer-manager-window and python itself are crashing (see screenshot).

Helmut

comment:8 Changed 8 years ago by cmbarton

Except for the bug I mentioned above, this works fine for me when I open a DEM from the Spearfish demo data.

If you'd like to try my build for OSX 10.6, you can download it at <http://www.public.asu.edu/~cmbarton/files/grass_mac/OSX10.6-snowleopard/>.

I am using the most recent of William Kyngesburye's frameworks.

Michael

comment:9 Changed 8 years ago by epifanio

Hi Michael,

i download your binary version for grass65 and i have the same behavioure :

gui window start at the top of the screen (i'm not able to move them) and if i select "3d view" in the map-display combo-box i have a gui crash (quit).

tomorrow at work i've access to ftp to upload a screen-record

comment:10 Changed 8 years ago by cmbarton

Have you installed the newest Mac frameworks?

comment:11 Changed 8 years ago by epifanio

Yes, i'm using the latest frameworks, seems to me that's a problem more related to python + wx + osx (i don't think the framewroks are affecting this problem)

at this link what happens on my mac :

https://files.me.com/epiesasha/6h9k0k.mov

comment:12 Changed 8 years ago by cmbarton

I see several errors popping up when you start. 1) you are missing NumPy? (in terminal), 2) some text shows up in the command window in the GUI, but it went by so fast that I could not see it.

Have you installed any other Python on your computer at any time, or in any other application?

Michael

comment:13 Changed 8 years ago by epifanio

Hi,

in the wx output window i have the "digitizer worning" :

Vector digitizer not available Reason: No module named grass6_wxvdigit Note that the wxGUI's vector digitizer is currently disabled (hopefully this will be fixed soon). Please keep an eye out for updated versions of GRASS. In the meantime you can use "v.digit" from the Develop Vector menu.

while on the shell i've a numpy "not found" error :

GRASS 6.5.svn (spearfish60):~ > profile.py: This module requires the NumPy? module, which could not be imported. It probably is not installed (it's not part of the standard Python distribution). See the Numeric Python site (http://numpy.scipy.org) for information on downloading source or binaries.

this is beacouse i'm using python 2.7 64bit and numpy, scipy and all my "python source build" are for 64bit arch.

this is is a problem of WX on OSX , the lack of a 64 bit version for wx ... make all the things more difficult. actually i really don't like the state of WX .. we're waiting a 64bit cocoa version from more than 2 years. i tried the 2.9 cocoa version and it is buggy as well.

comment:14 Changed 8 years ago by epifanio

Note, i tried to remove my python.framework (temporary) and build against the system python .. but nothing changes

comment:15 Changed 8 years ago by cmbarton

I'm pretty sure that this is a version mismatch problem. This is likely to be more of an issue with 6.5, in which both the digitizer and 3D visualizer are built with swig than in 7, where we switched to ctypes.

The GUI is built with Python 2.5 and will run on 2.6. There are reports that it will not run on 2.7 without errors.

If you have installed a 3rd party Python (e.g., Macpython), it is likely that you will run into trouble. Just removing the frameworks directory is not enough, as the actual files are in /usr or /usr/local (I don't remember which version ends up where) and there are path statements to remove in several places. Also, wxPython can end up in or the other versions for a variety of reasons. We package wxPython with the Mac GRASS app, but that won't help the version mismatches if other Python versions are installed.

Michael

comment:16 Changed 6 years ago by hamish

is this fixed? or possibly related to #1736?

comment:17 Changed 5 years ago by annakrat

Resolution: fixed
Status: newclosed

The ticket is 3 years old and a few things has changed since then so I am closing this ticket. Reopen if needed.

Note: See TracTickets for help on using tickets.