+- MacResource (https://forums.macresource.com)
+-- Forum: My Category (https://forums.macresource.com/forumdisplay.php?fid=1)
+--- Forum: Tips and Deals (https://forums.macresource.com/forumdisplay.php?fid=3)
+--- Thread: Kernal Panic stuff -- Camtasia doc has 22 threads and 1.7GB memory (/showthread.php?tid=143231)
Kernal Panic stuff -- Camtasia doc has 22 threads and 1.7GB memory - dmag - 10-23-2012
Hi,
I'm not sure this has anything to do with the recent kernal panic episodes I've had since my son dumped water on the MBP and it was resurrected, but...
In Activity Monitor I noticed that my Camtasia for Mac document (and there's only ONE document open, is showing 22 threads and is using 1.7gb of system memory.
Does that seem right?
The file is 350mb and has a ton of edits, but what's the 22 threads and could that have generated the kernal panic?
Thanks.
Re: Kernal Panic stuff -- Camtasia doc has 22 threads and 1.7GB memory - Chakravartin - 10-23-2012
dmag wrote:
In Activity Monitor I noticed that my Camtasia for Mac document (and there's only ONE document open, is showing 22 threads and is using 1.7gb of system memory.
Does that seem right?
No.
dmag wrote: The file is 350mb and has a ton of edits, but what's the 22 threads and could that have generated the kernal panic?
Threads:
http://en.wikipedia.org/wiki/Thread_%28computer_science%29
No, but it could crash for other reasons. Are you running the latest version of Camtasia?
If you think that's what's crashing you, try uninstalling it.
Re: Kernal Panic stuff -- Camtasia doc has 22 threads and 1.7GB memory - TheCaber - 10-23-2012
No, it is not likely that the number of threads would cause a kernel panic; the OS is multi-threaded by design and supports multi-threaded applications. You need to look at your system log file(s) to see what was active leading up to the panic(s).
Applications->Utilities->Console.app->Files->system.log
you could also see if there are any entries under the Crash Reporter twistie
all system activity logs are under the /private/var/log twistie, older logs are compressed with bz2 (which Console.app will uncompress to display/search).
Report back, please, if there are any Crash Reporter reports (wow, that's repetitive),
Re: Kernal Panic stuff -- Camtasia doc has 22 threads and 1.7GB memory - dmag - 10-23-2012
Nothing in the Crash Reporter.
I'm running Lion and the most current version of Camtasia.
Here's a symptom...
When I hit play in this document, it moves about a quarter of a second and then stops. Then, maybe five seconds pass and it moves again...maybe one second's worth along the timeline. This repeats several times until it begins to play normally, which is usually about 20-30 seconds after I initially hit the play button.
Not sure if that helps anything.
Thanks.
Re: Kernal Panic stuff -- Camtasia doc has 22 threads and 1.7GB memory - Chakravartin - 10-23-2012
dmag wrote:
When I hit play in this document, it moves about a quarter of a second and then stops. Then, maybe five seconds pass and it moves again...maybe one second's worth along the timeline. This repeats several times until it begins to play normally, which is usually about 20-30 seconds after I initially hit the play button.
Not sure if that helps anything.
It's caching. You need a faster hard drive.
Re: Kernal Panic stuff -- Camtasia doc has 22 threads and 1.7GB memory - dmag - 10-23-2012
Maybe, but this wasn't happening before the incident with the water, and the tech said the drive escaped without any problem. He tested it and it passed.
As well, every other app run has had no trouble.
I just figured that since Camtasia is video, maybe that was the issue...that it's drawing more resources.
Re: Kernal Panic stuff -- Camtasia doc has 22 threads and 1.7GB memory - modelamac - 10-23-2012
Why not uninstall it and test? It's super-easy to do and quick as well. Camtasia is causing the problem or not.
Re: Kernal Panic stuff -- Camtasia doc has 22 threads and 1.7GB memory - dmag - 10-23-2012
modelamac wrote:
Why not uninstall it and test? It's super-easy to do and quick as well. Camtasia is causing the problem or not.
Just about ready to do that. Hopefully, it's a corrupted app.
Thanks.