Mori 1.6.10 seems to have broken something 1.6.9 fixed

Tags ( )

Back in January, a couple of us had problems when Mori version 1.6.8 slowed to a crawl (http://apokalypsesoftware.com/products/node/2577).

Version 1.6.9 fixed that problem, but when I open that same file with version 1.6.10, as it starts to open, I see it re-indexing the search indexes. After Mori re-indexes the search indexes, my notebook opens, showing me the three windows I have created. However, as soon as the three windows open, the spinning color wheel appears and will stay until I finally force quit Mori. (At one point, I left the color wheel spinning for over an hour, but the spinning color wheel just kept spinning.)

If I force-quit Mori and re-launch it, the sample Mori.mori file opens fine, but when I try to open my own file, the file opens, showing my three windows, but then the spinning color wheel appears and stays. While the spinning color wheel is visible, I can click on any of the three windows I've saved for my document and Mori will bring that window to the fore, but the spinning color wheel just keeps spinning.

(Since I'd seen this problem when I first downloaded and tried v 1.6.10, before I tried 1.6.10 again, I had used Help/Check and Repair Notebook in version 1.6.9. This showed no problems with my file, although after I'd tried it again in version 1.6.10, version 1.6.9 did report errors in a copy which had shown no errors when 'Check and Repair Notebook' had been run previously.

Here is the Console log from running 'Check and Repair Notebook in v 1.6.9 _after_ having tried to open the notebook in 1.6.10:

Mac OS X Version 10.4.11 (Build 8S165)
2008-03-18 21:36:23 -0400
Mar 18 21:36:48 the-cam-v /usr/bin/java: Java is generating its shared archive, version 1.5
2008-03-18 21:39:03.072 Mori[390] WARN -[BKPluginRegistry validatePluginConnections] - no extension point found for plugin id: com.apokalypsesoftware.mori.MIUserInterface loadSequence: 2147483647's extension
2008-03-18 21:39:03.072 Mori[390] WARN -[BKPluginRegistry validatePluginConnections] - no extension point found for plugin id: com.apokalypsesoftware.mori.MIUserInterface loadSequence: 2147483647's extension
2008-03-18 21:44:57.826 Mori[484] WARN -[BKPluginRegistry validatePluginConnections] - no extension point found for plugin id: com.apokalypsesoftware.mori.MIUserInterface loadSequence: 2147483647's extension
2008-03-18 21:44:57.827 Mori[484] WARN -[BKPluginRegistry validatePluginConnections] - no extension point found for plugin id: com.apokalypsesoftware.mori.MIUserInterface loadSequence: 2147483647's extension
2008-03-18 21:50:57.027 Mori[484] note strings does not equal RTFD string for entry 'try Van's new greeting card service (note)'
note strings does not equal RTFD string for entry 'check for info on hacking, tools, &c'

I'm concerned that this problem, whatever it is, will keep my file from running in Mori 1.7 when it is released.

TIA for any help you can offer.

--Chris

I'm getting the same error

I'm getting the same error here. When I try to delete (CMD-K) I get the pinwheel of death. When I restart Mori and have it reindex, it finds everything that I was trying to delete and restores (some of) it. I've never seen this behavior before in Mori.

I went back and reinstalled

I went back and reinstalled 1.6.9 and it works just fine (AFAICT). I think that 1.6.10 should only be required for Leopard; those of us on Tiger will be better off with 1.6.9.

Something similar here, perhaps

I had crashes galore with one notebook when using mGTD, but upgrading to 1.6.9 have fixed that. Upgrading to 1.6.10 gets me the same trouble again.

It seems that alaskamike and

It seems that alaskamike and gomenqb are both on the right track.

At the moment I have the use of an Intel-based MacBook which is running Leopard. With alaskamike and gomenqb's posts in mind, I just did a little experiment. I copied the Mori 1.6.10 installer and my Mori data file (which works fine under Mori 1.6.9 and Tiger, but becomes 'unresponsive' when opened in Mori 1.6.10 and Tiger) to the MacBook, launched Mori 1.6.10, the opened the copy of my data file. All seemed fine, so it does appear that Mori 1.6.10 will work well under Leopard.

Then I copied the data file which had just been opened and run in Mori 1.6.10 back to my Tiger machine (a PPC Mac, FWIW), installed Mori 1.6.10 from the same installer, then opened the 'Getting Started' Mori file which comes with the installer. All seemed well. Then I closed the 'Getting Started' file and opened the copy of my own data file which had just run fine in Mori 1.6,10 under Leopard . . . and got the same 'unresponsive' problem.

So, it does seem that people who are running Tiger should stay with Mori 1.6.9, while those running Leopard apparently can run Mori 1.6.10 without having it freeze up and become 'unresponsive' as it does on machines running Tiger.

What this may mean for Mori 1.7 is anybody's guess . . . 8-)

HTH

--Chris

Does this problem still occur in Mori 1.6.11?

Keeping tabs. I want to get to the bottom of every case, and help every user enjoy a trouble-free Mori experience.

Alfonso

1.6.11

Seems to work fine so far. Mori crashed on me one time, when I was using the search box, but otherwise has been a good release.

Mike

1.6.11 Search Box Crash

Please send me the crash report. It can be found at "/Users/acct/Library/Logs/CrashReporter/Mori.crash.log" or "/Users/acct/Library/Logs/CrashReporter/Mori.exception.log".

The less of these little monsters that are running around, the happier we will all be.

Thanks,
Alfonso

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.