edit group then crash

[billworld]

I've had a few instances of selecting a group of objects then selecting the Edit Group command and having RR crash on me. I've tried copy/pasting the offending group into a new stack and doing the same there does not contribute to a crash (although the islocked, canbeselected [or whatever the actual terms are] states for these objects in the new stack may be different.

Have any of you run into this problem of RR crashing when attempting to edit a group?

[Janschenkel]

Can't say that I have encountered similar crashes. That being said, any crashes should be reported to http://quality.runrev.com along with the crash log - that's the best way to ensure these get fixed asap.

To get the crash log under MacOSX, use the 'Console' application (which you can find in the Utilities subfolder of the Applications folder. Go to log file '~/Library/Logs/CrashReporter/Revolution.crash.log' and copy the last crash log block which should start with something like

Code: Select all

**********

Host Name:      imac-g5-van-jan-schenkel
Date/Time:      2007-06-05 19:50:33.905 +0200
OS Version:     10.4.9 (Build 8P135)
Report Version: 4

Command: Revolution
Path:    /Applications/Revolution Enterprise/2.8.1-gm-1/Revolution.app/Contents/MacOS/Revolution
Parent:  WindowServer [63]

Version: 2.8.1.470 (2.8.1.470)

PID:    3894
Thread: 0

Exception:  EXC_BAD_ACCESS (0x0001)
Codes:      KERN_PROTECTION_FAILURE (0x0002) at 0x000001ab

Thread 0 Crashed:
...

(Yes, it has been over a year since Revolution crashed on this machine, and I use it daily)

Jan Schenkel.

[billworld]

Excellent. Will do next time this occurs. Thanks.

Can't say that I have encountered similar crashes. That being said, any crashes should be reported to http://quality.runrev.com along with the crash log - that's the best way to ensure these get fixed asap.

To get the crash log under MacOSX, use the 'Console' application (which you can find in the Utilities subfolder of the Applications folder. Go to log file '~/Library/Logs/CrashReporter/Revolution.crash.log' and copy the last crash log block which should start with something like

Code: Select all

**********

Host Name:      imac-g5-van-jan-schenkel
Date/Time:      2007-06-05 19:50:33.905 +0200
OS Version:     10.4.9 (Build 8P135)
Report Version: 4

Command: Revolution
Path:    /Applications/Revolution Enterprise/2.8.1-gm-1/Revolution.app/Contents/MacOS/Revolution
Parent:  WindowServer [63]

Version: 2.8.1.470 (2.8.1.470)

PID:    3894
Thread: 0

Exception:  EXC_BAD_ACCESS (0x0001)
Codes:      KERN_PROTECTION_FAILURE (0x0002) at 0x000001ab

Thread 0 Crashed:
...

(Yes, it has been over a year since Revolution crashed on this machine, and I use it daily)

Jan Schenkel.

[EddieColumbus]

I experienced a crash while working with one of the tutorials. I was able to eventually duplicate it on demand. I found the issue documented and appended my info on how to duplicate.

http://quality.runrev.com/qacenter/show_bug.cgi?id=7389

[billworld]

Thanks Eddie for posting the details. Hopefully this one will get fixed quickly.

I experienced a crash while working with one of the tutorials. I was able to eventually duplicate it on demand. I found the issue documented and appended my info on how to duplicate.

http://quality.runrev.com/qacenter/show_bug.cgi?id=7389

[FourthWorld]

Excellent diagnostics, Eddie. Thanks for adding to that report.

[mwieder]

W00t! This is great news. I was able to replicate the crash immediately by following the recipe using your test stack. Thanks for narrowing this down.