On 2006-07-12, at 8:07 PM, Phil M wrote:
On Jul 12, 2006, at 1:41 PM, Ken Ampel wrote:
I just wanted to support what Sven has been saying.
I program exclusively on Mac and for all releases except for
the most current one, the color chooser window will cause RB to
crash without warning.
I am usually constructing a standard window when this happens.
It is very sporadic and unpredictable, usually occurring only
after I've been working for an hour or so. In other words, you can
open the color chooser 10 times without a problem, and the next
time it might do it.
You can usually tell when it is about to happen, because you
select the button to choose the color chooser window, and there is
a delay while RB's wheels spin (you can hear the gears whirring),
and then the whole program suddenly drops out. I have not been
able to pick out any associated events or conditions that might
contribute to the problem. The time the crash occurs seems similar
to all the other times when the color window opens normally. It
could be a memory allocation issue, but that's only a guess.
I have not reported this since I keep expecting RB to fix it,
having assumed that they are aware of this, since, even though the
crashes seem random, it does occur on a somewhat regular basis
when working for long periods, and I assume that they too must be
experiencing the same problem.
As I say, I haven't experienced this problem on 2006 release
three, but apparently it is still a problem, since Sven is noting it.
I think that Sven is getting frustrated with our responses, and in
no way am I trying to scoff at him or this issue -- and I don't
think that anyone else is either.
I think this is a *very* serious issue and I want to see it resolved.
Unfortunately, I have not experienced this crash and if this issue
only occurs sporadically, then it is unlikely that REAL Software
has experienced it either. I created a project to try to test this
issue based on what you and Sven wrote in the emails, and I am not
able to get it to crash. So this means that either I am not using
the same steps/objects that you are using or my machine/software
does not have this issue. Even if REAL Software is reading this
thread, there are a number of unanswered questions which should be
addressed before a formal report can be submitted.
1. Can you crash with my sample project?
2. When does the crash occur:
a) first attempt after launch
b) random attempts throughout a single run
3. Have you looked at the CrashReporter crash log?
4. If you have distributed apps to your customers with this
problem, have users reported it?
5. Which Mac OS are you running?
6. Is the App compiled as PEF or Mach-O.
While the Crash Report may be difficult to understand, it can be a
valuable tool to know if it is your code, RB or Apple code which
ultimately croaked. However, a Crash Log is not ideal since it
does not list the steps required to reproduce the problem -- which
means the Crash Log can explain the how but not the why. But if
there is nothing else, please submit that with a report or at least
post it to this list. Make sure you only take the last entry since
the Crash Log will contain all the app crashes since the last time
the log was cleared. Also, make sure you have "Include Function
Names" enabled in the App class or compile the app as Mach-O.
Here is the link to my project again... please test it and see if I
wrote it correctly:
http://developer.dreystone.com/bugs/fpt.rbp.zip
But please, understand that test this problem, is not done in one
hour or two hours, perhaps 20 hours...
When i tested r3, i doing it about 500-600 times and it take more
than two hours... And i was just to say YEEEAAA they fixed it when it
crash two times in 5 minutes...
And for me this session is at the end.. Never, never and again never ...
Sven E
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
