The Omni Group
These forums are now read-only. Please visit our new forums to participate in discussion. A new account will be required to post in the new forums. For more info on the switch, see this post. Thank you!

Go Back   The Omni Group Forums > OmniGraffle > OmniGraffle General
FAQ Members List Calendar Search Today's Posts Mark Forums Read

 
Save issue Thread Tools Search this Thread Display Modes
Hello,

I'm looking at OmniGraffle and like it a lot, but the trial version (with a trial key) is causing me trouble. If I hit ⌘-s to Save a document a bunch of times (anywhere from 5 to 20 times) in a row, the machine crashes. This only happens with OmniGraffle, my other apps are fine. It happens with with either my USB M$ Natural Keyboard or the MacBook Pro's built-in keyboard.

I'm thinking it has something to do with the trial license, but am not sure.

This is on a brand new MacBook Pro:

Model Name: MacBook Pro
Model Identifier: MacBookPro3,1
Processor Name: Intel Core 2 Duo
Processor Speed: 2.4 GHz
Number Of Processors: 1
Total Number Of Cores: 2
L2 Cache (per processor): 4 MB
Memory: 2 GB

Here's the info on the OmniGraffle I have installed:

OmniGraffle 4:

Version: 4.2
Last Modified: 7/18/07 4:44 PM
Kind: Universal
Get Info String: OmniGraffle 4.2, version 129.12, Copyright 2000-2007 The Omni Group
Location: /Applications/OmniGraffle 4.app

I don't even know how to start debugging this, it seems very odd that an application Save could crash the machine. I know OmniGraffle checks the number of objects on a save, but this happens on empty docs and docs with less than 20 objects...any ideas?
 
Thanks for the heads-up. I've reproduced this in-house even without a trial license, unfortunately. Given that the whole machine crashes, not just Graffle, we'll probably have to collaborate with Apple to get this addressed.

Out of curiosity, why are you saving several times in a row?
 
Wow - good to hear it's reproduceable.

I tend to hit command-s out of habit when I'm working...partly to save the doc but mostly because it helps me think.

mouse-click-type-type-mouse-click-hm...need to think a bit...command-s...commans-s...command-s...mouse-click-mouse-click

Out of curiosity, what could a drawing application do that would cause the kernel to crash?
 
It could be a fundamental flaw in OS X - does it happen when you do it in other apps?
 
I've tried against TextEdit and OmniOutliner, with no kernel panics, however that doesn't count them out. It could just be a random thing and the few times we've tested against Graffle it happened to panic in the first couple of minutes while holding down Command-S to repeatedly save.
__________________
"Vroom! Vroom!!"
 
It doesn't seem to happen in other apps I use a lot - word, eclipse, or vim.

I also ran tech tools against my machine, which does a bunch of disk writes, and had no problem.
 
Well, now I can't reproduce it.

The only thing I can think of that I did between then and now is that I removed Norton Anti Virus from the system.

I had disabled the NAV feature that interfered with disk activity because it slows down I/O operations way too much. Maybe even when it's disabled, the NAV kext intercepts reads and writes...and maybe there was a race condition between OmniGraffle and NAV?

Hard to say without a reproducable test case...
 
I had 4 Kernel Panic in my Mac in the last days. All the 4 Kernel Panic occurred when I hit the keys Command + S in OmniGraffle. I had no Kernel Panic in other applications. The only thing in common in the four Kernel Panics is that all occurred when I hit the Save key sequence.

This problem is no deterministic as I can Save without problem. I'm currently doing processes diagram flow in the past four days so I saved several OmniGraffle documents hundreds of times.

Setup:
MacBook Pro ( 1 series ) 1.83 GHz 2G Ram.
MacOS X 10.4.10 with all the security updates.
OmniGraffle Pro version 4.2 (v129.12). Educational License.

From panic.log

Thu Aug 9 10:34:15 2007
panic(cpu 0 caller 0x001D2919): vnode_put(60348c4): iocount < 1
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x2503b628 : 0x128d08 (0x3cc0a4 0x2503b64c 0x131de5 0x0)
0x2503b668 : 0x1d2919 (0x3d4f30 0x60348c4 0x2503b6b8 0x1c4cd5)
0x2503b698 : 0x1d29cf (0x60348c4 0x1 0x3f5f0a8 0x60348c4)
0x2503b6b8 : 0x1f623c (0x60348c4 0x2503b7e8 0x3a44d50 0x2503bf34)
0x2503b808 : 0x1f645b (0x2503bf34 0x2503b884 0xa 0x13bdec)
0x2503b8a8 : 0x1e5038 (0x2503b8c8 0x2503b8dc 0x2503bf34 0x0)
0x2503b8f8 : 0x1ccc89 (0x3a8539c 0x2503bac4 0x2503bbd8 0x2503bf34)
0x2503b968 : 0x1cd4af (0x2503baac 0x100 0x2503bacc 0x0)
0x2503ba18 : 0x1bdf09 (0x2503baac 0x202 0x2503ba88 0x1416ad)
0x2503bf58 : 0x37ad83 (0x3e79bb8 0x40a0090 0x40a00d4 0x0)
0x2503bfc8 : 0x19b28e (0x40ebf58 0x0 0x19e0b5 0x40ebf58) No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xbfffd318

Kernel version:
Darwin Kernel Version 8.10.1: Wed May 23 16:33:00 PDT 2007; root:xnu-792.22.5~1/RELEASE_I386


*********

I've stopped saving and just let OmniGraffle auto-save feature save the documents. But sometimes I just hit Command + S as a reflex behaviour after editing the document.

Any ideas?
 
I'll try the beta release. Just for the records I had no Kernel Panic since I stopped saving while editing in OmniGraffle and relied on auto save feature saving only when was time to close the document.
 
 


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Similar Threads
Thread Thread Starter Forum Replies Last Post
Issue regarding bar Sync100 OmniFocus 1 for Mac 0 2013-03-15 02:59 AM
Due Soon Issue gotung OmniFocus for iPhone 0 2008-11-07 09:05 AM
AutoFill 'Always save' vs AutoComplete 'Always save' Gregory OmniWeb Bug Reports 1 2008-07-31 10:05 PM
? CSS issue with OW pheski OmniWeb Bug Reports 4 2006-10-26 04:11 PM
Save window size doesn't save position zottel OmniWeb Bug Reports 3 2006-08-29 03:33 PM


All times are GMT -8. The time now is 01:22 PM.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2019, vBulletin Solutions, Inc.