James Hale wrote:
Richard Gaskin wrote
It would be helpful to check this under the current versions of v7 and
v7 (7.1.3rc1 and 8.0dp15 respectively), and if the crash recurs in
either please submit a bug report.
Interestingly I attempted to do just that. But rather than threaten the app
I am working on (one crash did strange things to all the fonts on relaunch)
I decided to make a test stack to submit.
This was both good news and bad news.
Bad news: Couldn't reproduce the crash - obviously not simply what I
initially thought.
Good news: In trying to reproduce the crash I ended up getting the DG to
work as I originally wanted.
Moral of the story: Making a simplified stack to demonstrate a "bug" can
bring all sorts of gifts.
Hmmmm...now I have that nagging awareness of a crasher bug somewhere in
the engine...
If you have time it might be helpful to make a copy of your stack and
try that in v8 again, and if you get a reproducible recipe send a report
to the team and make arrangements to send that stack to them separately
(they're quite good about working with proprietary stacks and disposing
of them once they've resolved the issue).
On the other hand, it may just be bit rot. I've seen that with some
JPEGs in my archives, and while rare it could affect any file. Storage
devices and RAM are as imperfect as everything else we work with on this
planet (one more reason to spring the extra bugs for ECC RAM when you
mobo supports it).
--
Richard Gaskin
Fourth World Systems
Software Design and Development for the Desktop, Mobile, and the Web
____________________________________________________________________
[email protected] http://www.FourthWorld.com
_______________________________________________
use-livecode mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
