We are currently migrating Bugzilla to GitHub issues.
Any changes made to the bug tracker now will be lost, so please do not post new bugs or make changes to them.
When we're done, all bug URLs will redirect to their equivalent location on the new bug tracker.

Bug 480 - Freezes coz of newly added key composition support
Summary: Freezes coz of newly added key composition support
Status: RESOLVED DUPLICATE of bug 471
Alias: None
Product: SDL
Classification: Unclassified
Component: video (show other bugs)
Version: 1.2.12
Hardware: PowerPC Mac OS X (All)
: P2 blocker
Assignee: Christian Walther
QA Contact: Sam Lantinga
URL: http://www.managames.com
Keywords:
Depends on:
Blocks:
 
Reported: 2007-08-18 23:12 UTC by manutoo
Modified: 2007-08-20 23:52 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description manutoo 2007-08-18 23:12:46 UTC
I reported freezes on the newsgroup here : http://article.gmane.org/gmane.comp.lib.sdl/34324

console.log contains :
"2007-08-18 08:48:22.368 Tennis Elbow 2006[277] Exception raised during posting
of notification. Ignored. exception: *** -[NSLayoutManager
glyphRangeForTextContainer:]: given container does not appear in the list of
containers for this NSLayoutManager."

someone said he had the same trouble but with SDL 1.3 and pointed out this revision :
http://libsdl.org/cgi/viewvc.cgi?view=rev&revision=3217

Then, I commented out these lines :
1- [field_edit interpretKeyEvents:[NSArray arrayWithObject:event]];
2- field_edit =  [[NSTextView alloc] initWithFrame:r];

and now, the freezes seem to be gone ! (at least on my system, I still need to get confirmation from my users).
Comment 1 manutoo 2007-08-19 05:46:29 UTC
One user just reported he didn't have freeze anymore and it also corrected the slowness he was experiencing on his G4 dual, OSX 10.4, GeForce4 MX AGP 64MB .
Comment 2 Will Glynn 2007-08-20 13:58:02 UTC
Seconded. I see occasional-to-frequent crashes in an entirely distinct code base giving the same message on the console, though I haven't tried that workaround yet. I found this bug report via the below discussion as indexed by Google.
Comment 3 Sam Lantinga 2007-08-20 23:52:03 UTC

*** This bug has been marked as a duplicate of bug 471 ***