P45 Neo2-FR hangs during large file moves

Hello all,
I have a newly built system that I moved my old XP install onto. ( Removed old Video and hardware drivers then did a repair install on the new hardware. ) That process appears to have been successful. The system runs normally most of the time, including resource heavy 3D apps like SecondLife. I have also accumulated over 32 hours running memtest86 with no errors found. ( a 24 hours session and an 8+ hour one. )
During the upgrade/rebuild I backed up almost 0.5TB of data onto an external drive and I'm not trying to move those files onto the new RAID array or a partition on the main hard drive. During any large copy operation, the system locks up. It's usually several minutes into the copy, and a hard reset is required to recover. The external drive is formatted to FAT32, so I've already addressed file size limitations as I copied the data to the external. The external drive is USB/Firewire/eSATA, but so far I've only used USB on the new hardware due to a lack of cables.
Anyone seen something like this before ? I'd really like to get the files back onto my internal drives. The external is a loaner from a friend, so there's a little time pressure. Any help will be appreciated.
Thanks
Todd

Update on this. I have not done a reinstall to date since I don't have a spare hard drive on which to do so.
However, I can eliminate a windows or driver problem from the list. I see exactly the same symptoms - random hangs of the machine - under Ubuntu 8 as well as windows. The Linux install is clean from a downloaded image and updated as recommended by the package manager.
It seems that the most likely time for the system to hang is during periods of intense IO activity. I had thought it was large file copies because that was what I was doing a lot of at the time of my original post.
I have tried moving my video card to the first PCI-X slot. No change.
I have removed 2 of the 4 memory modules, leaving 2x2Gb installed in bank 0. No change.
I have added extra fans - a large on on the side of the hard drive bay ( The case is an Antec Sonata III ) and a smaller fan aimed at the memory. No change.
I am using the J-micron Raid controller - is this still problematic ? I seem to recall some mentions of this.
Any suggestions to help isolate the problem would be appreciated.

Similar Messages

Mail hang during large message download

I've noticed several times when I get emails that either exceed the auto download size threshold, or have large attachments on them that Mail will 'hang' during the download. I can exit out of the message but it's still spinning away and won't get any more email from the server.
I'm using a Pop email account. The only fix I've found is to "magic power cycle" the mail app using the sleep button / home key hold down. Once mail starts after this the message will fully download. It's been happening for a while, but I wanted to be sure it wasn't a fluke.
Anyone else run across this & find an easier workaround?
Thanks,
Dave

I have been having no end of problems with email since upgrading to 10.5 about a month ago.
Generally, after some time, various activities hang around in the Activity window (such as "evaluating message n of m") and prevent normal email updates and quitting. Neither Apple support nor the local Apple Genius were able to assist. Even reinstalling the OS (10.5.2, 10.5.3, or 10.5.4) and rebuilding the user account manually did not work. I tried running "Sample Process" in Activity Monitor on Mail.app and noticed a lot of "semaphorewait_signaltrap"s that seemed to be related to AddressBook. This led me to the following process which has (at least for now) fixed my problem:
1. Quit (or Force Quit) Mail.
2. In Address Book, use File>Export>Address Book Archive... to dump the contents of the address book.
3. Quit Address Book
4. Rename your ~/Library/Application Support/Address Book folder to something else (in case you want to restore it later)
5. Start Address Book
6. Use File>Import>Address Book Archive... to restore the contents of the address book
It may be voodoo, but it worked for me.

Photoshop Elements 11 Organizer failed during folder / file move

I have a large image collection, in excess of 40,000. I'm running on a PC with Windows 7 and all updates installed. I just purchased PSE 11 to replace PSE 10. After installing PSE 11 I converted my catalog. That seemed to go OK. At that point I discovered that my C: drive was almost full so I decided to move my image collection from its C: drive location to an external hard drive that had sufficient capacity. In order to ensure the integrity of the catalog I decided that I should use the PSE 11 Organizer to move the files. This would allow the Organizer to update the location information for the files as it moved them, although it was clear that this would take many hours to complete. So, using Organizer I did a "drag and drop" of my image collection's root file from the C: location to the external drive which happened to be the J: drive. Organizer appeared to be running properly so I left it to continue overnight. The next morning I discovered that only about 2/3 of the files had been moved. There was a very cryptic message that said the opertion could not be completed because of "...possibly unsupported files types, files with read only attributes.." etc. I did not write down the actual message and it did not tell me where in the transfer the failure occurred. After doing some detective work I discovered that many folders and files had been copied to the J: drive that were not appearing in the Organizer catalog and consequently were not being displayed. Some folders had only a portion of their files copied. Fortunately, the files were still visible and cataloged on the C: drive. I did look at my files on the C: drive and there were some that for what ever reason had read only attributes.
I don't have a good guess as to what was actually the root cause of the problem, but here's how I think the file movement should happen. The selected file, files, or folders should be copied to the specified destination. At that point they should be added to the catalog, then the files should be deleted from their original location and the catalog updated accordingly. If an original file is read only then it can't be deleted but the attempt to delete it should be reported as an inability to delete with no consequences imposed on the files that have been placed in their new location. The "problem" should not be promoted to the status of a serious or fatal error that causes only partial completion of the overall operation.

Bill Junk wrote:
I've seen a couple postings in the forum that related to catalog conversion failures and suggested that they could be avoided by running in administrative mode. When I did my conversion is was not in administrative mode and it's certainly possible that there were files with restrictive permission settings that screwed things up. It's also fairly likely that the catalog itself had some issues that were not detected or fixed by running a catalog repair.
That's something I had the opportunity to test today : after a fresh install of my second copy of PSE11 on another computer (Vista), I first restored without problem a PSE11 backup from the other computer (XP). Then I tried a restore for a catalog from a PSE6 version on the second computer. The conversion failed the first time and worked the second time when run as administrator. This time, I don't think there were file types problems, since that PSE6 catalog had been restored successfully on a PSE10 version some months ago. I really don't understand that 'administrator' problem, since all my files are situated in a second internal 1 Tb drive with full access for my account ?
I am not sure about the details of your case, but I understand you have restored exactly the same tree structure in a new J: drive. Your catalog is always accessible in its original location.
In that case it's possible to simply create a copy of your catalog (a simple copy of the folder containing the database catalog.pseXXdb - to be found in the help menu, system info). Then you need a sqlite database management tool (I use the add-on sqlite manager in Firefox) to simply edit a single record in a table containing the identification of all drives known to the catalog. You simply edit the letter and the serial number of the drive (DOS command VOL:).
I had a case where I had a catalog and all the media on an external drive. That external drive was assigned a different letter in different computers. Either I used the above solution, or I had to reassign drive letters in one of the computers.

Java.io.IOException during large file processing on PI 7.1

Hello Colleagues,
for a large file scenario on our PI 7.1 System we have to verify with big file size we are able to process over PI.
During handing over the large file (200 MB XML) form the Adapter Frame Work (File Adapter) to the Integration Engine we receive following error:
Transmitting the message to endpoint http://<host>:<port>/sap/xi/engine?type=entry using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error transmitting the message over HTTP. Reason: java.io.IOException: Error writing to server.
The message processing stopped and message still lies at Adapter Frame Work. Large files up to 100 MB we are able to process successfully.
Please, could you tell me why this happened and how we are able to solve it?
Because there is not a java.outofmemory exception however a IO exception i think it could be an memory issue?!
Many thanks in advance!
Regards,
Jochen

Hi Jochen,
Indeed the error is IO Error and it is because the Adapter engine was not able to send the message to Integration server. But it happens due to memory/heap size issues.
Look at these thread, they are having the same problem. Please try the remedy measures suggested by them
Mail to Proxy scenario with attachment. AF channel error.
Error with huge file
problem with big file in file-to-proxy scenario
Is there any additional information in Adapter messaging tool.?
Regards
Suraj
Edited by: S.R.Suraj on Oct 1, 2009 8:55 AM

TimeCapsule (and AirPort extreme too) hangs on large file transfers

Greetings,
I got a following problem. I had install AirPort connected to my router with copper and extend network with TimeCapsule. TimeCapsule have two USB drives attached, AirPort - one USB. When I am transferring a large file, in a magnitude 2-3Gb or multiple simultaneous transfers of smaller files to/from those USB drives, depending on which drive I am using the AirPort or TimeCapsule get crashed. For plain user it is looks like as of sudden, data transfer stops, led in a front keeps green, and I can not reconnect to the drives. If I powercycle TC or AES everything get back to normal. Are there anyone else experiencing the same issues and if yes, what would be solution ?
Thank you.

I think we have tried almost every combination of disabling Large Send Offload, TCP offload, IP SEC Offloading, VMQ and Receive Side Scaling possible - in the various places there are - although I will be quite honest - as there are 3 places to do this
for each Server (the related physical and virtual NICs on the HV Server, and also the NIC in the VM) it is possible we may have missed an iteration...
During our testing we have noticed that the symptoms of the problem gets worse the higher the transfer speed is. For example if you transfer to the VM from a desktop with a 100Mbs NIC, there will be subtle lag and a transfer speed of say 10 or so KBs ,
if you use a device with a 1Gbs NIC, you on average achieve 50-70 KBs transfer speeds and the higher the number, the worse the GUI / Server locks up (although the transfer completes just fine).
We also tried throttling the bandwidth via the 2012 GUI - to see if that helped, but none of the changes we made seemed to work, and we did not have time to try the powershell way of doing this.
We did replace one of the VM's NIC with a legacy one as part of our testing today, and now data transfers to the VM from a PC with a 1Gbs NIC run slower at around 30-35 KBs and the are no noticeable GUI freezes, although during the large transfer
it looks like 1 in every 30-40 packets is dropped in a continual ping that runs during the transfer period.
We have done a lot of cable replacing today (out of diligence) but there seems to be no noticeable issue. We also tried and older NC380T dual port NIC we had available and used the standard driver Windows offered instead of an HP one, but the problem
was identical no matter which NIC we used.

External USB Hard Drive disconnects during large file transfers.

I have a Western Digital 2TB USB Hard Drive that Ive been using perfectly for a couple of years on my MacBook Pro. A couple of months ago I bought a 27inch iMac and started using it as my main computer. So I had that hard drive connected to my iMac.
I started to notice that during large transfers (be it many files or 1 big one), usually into the Gigs, I suddenly got a warning message saying that the Hard Drive was inappropriately disconnected. It doesnt appear in Disk Utility so I have to manually connect and disconnect the drive in order for it to show up again on the iMac. I tested it again on my MacBook and the same thing happened.
Another problem:
Sometimes it will dissappear from the iMac without a warning message, it just doesnt show up. (Usually after long periods of inactivity). I then have to manually disconnect and connect for it to show up.
So what do you think? Is my Hard Drive Dying?

I've been having similar problems with Lion on both external USB2 drive docks and more recently a Mediasonic 4 bay Firewire RAID drive. It was suggested that powersaving mode shut these down but changing that didn't completely solve the problem. I'm returning the Mediasonic for a replacement but suspect that it is something in the OS that is causing it.
If the replaced drive still causes the problem, I'll do a rebuilt of the system, eliminating apps that were migrated over, even though the system is only 5 months old. If anyone has solved similar issues, please let me know as well. Thanks.

GB crashing during large file export

GB 09 is crashing during an export of a project that is 2 hours and 20 min. I've tried diff export settings but the program still quits when it reaches about 3/4 of the project length.
No crashes in the past. Been exporting the project to rough cuts at various lengths from1 hour to 1 1/2, but upon finalizing the project, which happen to total over 2 hours, it can't make it through an export.
It's an audio book - talking only -no effects, other instruments, very straight forward.
I've tried exporting from the master .book file and a version with all the clips joined, tracks locked, and extra stuff deleted for project.
Here is some of the crash report (just pasting the first page of the crash report).
Process: GarageBand [2716]
Path: /Applications/GarageBand.app/Contents/MacOS/GarageBand
Identifier: com.apple.garageband
Version: 5.1 (398)
Build Info: GarageBand_App-3980000~2
Code Type: X86 (Native)
Parent Process: launchd [138]
Date/Time: 2010-03-29 11:14:16.969 -0400
OS Version: Mac OS X 10.6.2 (10C540)
Report Version: 6
Interval Since Last Report: 1758706 sec
Crashes Since Last Report: 39
Per-App Interval Since Last Report: 219501 sec
Per-App Crashes Since Last Report: 6
Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Thread 0 Crashed: Dispatch queue: com.apple.main-thread
0 com.apple.CoreFoundation 0x94dd0554 CFRelease + 196
1 com.apple.AppKit 0x9468967a -[NSBitmapImageRep initWithFocusedViewRect:] + 2257
2 com.apple.garageband 0x001f5fea 0x1000 + 2052074
3 com.apple.garageband 0x00205650 0x1000 + 2115152
4 com.apple.garageband 0x0014f7c2 0x1000 + 1370050
5 com.apple.garageband 0x0015a58a 0x1000 + 1414538
6 com.apple.AppKit 0x945edb6c -[NSView _drawRect:clip:] + 3721
7 com.apple.AppKit 0x945eb238 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 2217
8 com.apple.AppKit 0x945ebbcb -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 4668
9 com.apple.AppKit 0x945ebbcb -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 4668
10 com.apple.AppKit 0x945ebbcb -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 4668
11 com.apple.AppKit 0x945ebbcb -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 4668
12 com.apple.AppKit 0x945ebbcb -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 4668
13 com.apple.AppKit 0x945ebbcb -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 4668
14 com.apple.AppKit 0x945ebbcb -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 4668
15 com.apple.AppKit 0x945ebbcb -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 4668
16 com.apple.AppKit 0x945ebbcb -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 4668
17 com.apple.AppKit 0x945ebbcb -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 4668
18 com.apple.AppKit 0x945ebbcb -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 4668
19 com.apple.AppKit 0x945ebbcb -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 4668
20 com.apple.AppKit 0x94689b5f -[NSNextStepFrame _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 311
21 com.apple.AppKit 0x945e7111 -[NSView _displayRectIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:] + 3309
22 com.apple.AppKit 0x94547d6e -[NSView displayIfNeeded] + 818
23 com.apple.AppKit 0x944fb9c5 -[NSNextStepFrame displayIfNeeded] + 98
24 com.apple.AppKit 0x94511094 -[NSWindow displayIfNeeded] + 204
25 com.apple.AppKit 0x945425aa _handleWindowNeedsDisplay + 696
26 com.apple.CoreFoundation 0x94e43892 __CFRunLoopDoObservers + 1186
27 com.apple.CoreFoundation 0x94e0018d __CFRunLoopRun + 557
28 com.apple.CoreFoundation 0x94dff864 CFRunLoopRunSpecific + 452
29 com.apple.CoreFoundation 0x94dff691 CFRunLoopRunInMode + 97

Sorry about listing too much data from the GB crash report.
Anyone have trouble shooing tips for crashing during large mix downs/exports?
The file that crashes during export is over 2 hours long, but only 1 voice track with no effects!

Getting error 8 during a file move with shortcuts

Hello,
I am using the file move vi to move files and shortcuts from one folder to another. This works file when I am trying to move files. but when I try to move a shortcut (a file with a extension of *.lnk) the move vi fails and gets a error 8 (permission error). Why is this happening? I am assuming that a shortcut is a file, so I am treating it as a file and therefore expecting the move vi to move the shortcut from one folder to another.
Regards,
Kaspar

It could be that this is related to a bug that has already been discovered and reported. Our R&D deparment is working on it. When LabVIEW copies or moves a shortcut, it actually makes a copy of the file that is the target of the shortcut. However, it adds the ".lnk" extension to the end of the file name. This causes the new file to show up like a shortcut in Windows, but it is not a shortcut. If you rename the file and remove the ".lnk", then the file (the target of the original shortcut) will open without problem.
One workaround it to use the System Exec VI to copy the file from the Windows command line. See the attached VIs.
Jeremy P.
Applications Engineer
National Instruments
Attachments:
Move with Command Line for LNK.vi ‏16 KB
Copy with Command Line for LNK.vi ‏36 KB

Network Drive Losing Connection During Large File Transfer...

Hey, everyone.
Recently bought an Airport Extreme and LaCie USB HDD/Hub for my hybrid Windows/Mac home network. I formatted the drive with FAT32 as instructed, and hooked it up.
My first order of business was to back up all of my media on my Windows desktop machine, but it hasn't been working out so well. A short while after starting the 35+ gig transfer (a few minutes at most), I get an error message saying the the destination folder is no longer there. Sure enough, checking 'My Computer' shows that the drive is now a 'Disconnted Network Drive'.
Cycling power on everything and rebooting Windows restores the network drive, but the core problem remains.
Anyone else seen this and have any idea how to deal with it?
Thanks in advance for any help.

Hi,
I'm having the same problem. Here's the relevant parts of my setup:
Airport Extreme
HP printer and Western Digital "My Book" 500 G USB drive connected by 4/1 usb splitter
MacBookPro connected via Gigabit
Windows XP PC connected via Gigabit
My media I loaded on the usb drive by directly connecting the usb to my PC, I've also loaded other iTunes media to the usb drive from the mac book. If I point iTunes on the PC at the usb drive I can play the media just fine. When I try to copy large files (700 MB) from my PC to the usb drive (via the airport) I'm told the destination folder isn't there. I've also noticed the windows tooltips telling me that it lost the internet connection, and if I have the airport utility open on my mac it also looses the airport for a few seconds. I am able to copy small files (largest that's worked so far is 1.6 MB) the usb drive via the airport.

Search Index hangs on large files

I am using the 6.1 SP4 Web Server on Windows XP. I have the default search application working. My problem is adding MS Word documents to the collection. Word documents of the size 25KB work, but when I add a large Word document 6934KB it just hangs with no CPU activity going on.
Is there a work around or a parameter that needs to changed to allow larger sized files to be indexed in the collection?

I'm not sure what's going wrong, but you may want to try increasing the amount of memory the search indexer is allowed to use. To do this, you'll need to modify the searchadmin.bat batch file. You can find it in your Web Server's bin\https\bin subdirectory.
First, make a backup copy of searchadmin.bat. Next, open searchadmin.bat in a text editor and replace "-Xmx128m" with "-Xmx1024m". This will allow the search indexer to use up to 8x more memory.
Please let us know whether this helps.

Disk Utility hangs during DMG file creation

I use disk utility to create DMG files from folders (with the corresponding command from the File -> New menu). Every now and then (and quite often, really), Disk Utility will not complete this process, but instead hang forever. It seems that something in the kernel gets stuck, because the machine can get increasingly unresponsive after the hang has started (for instance, I wanted to look in the system log right now, but running less on /var/log/system.log would create long hangs on the whole UI). The only way out is a reboot.
The machine is otherwise very stable.
(Ah, and Time Machine started at the same time now, and doesn't seem to be able to run - maybe disk utility and time machine are creating some deadlock situation?)
Anyone who has seen similar behaviour?

I haven't had this issue this since upgrading to Snow Leopard, so I assume it has been fixed.

PE Hangs during peak file generation

I have experienced numerous hangs when PE8 trys to generate peak files for AVI files captured with WMM and Corel Video Studio X2 Pro.
I have seen the problem occur on various size AVI files from 1M to 9G. In all cases the audio is erratic ( soft and loud sounds usually at the end of the clip when the camera recording is terminated ) when playing it in WMP.
I took took the problematic AVI's and then used WMM or dvdate to "Save as AVI" file and then imported back into PE8 and the peak files were then genrated without issue.
Seems to me that this problem has existed in several PE releases. I wonder why the peak file generation routine does not either timeout after sometime or give the user the ability to cancel the operation and return control back to PE when these problematic files are encounter. It is annoying to have to kill PE from task manager when this occurs. Has anyone found a way to kill the peak file generation when this problem occurs without having to kill PE ?
Thanks
Mike

Hi Bill,
I have attached screen captures of gspot with AVI's captured with WMM and corel, look like they both import as type I avi's.
I have not had a chance to recreate the problem I originally saw, it will probably have to wait till the weekend when I have time to re-import the footage from the camera.
Thanks for your help.
Mike

In making a "highlights" movie, using clips from different imported iMovie events, can I delete the larger iMovie event file from the Events browser and still work w the smaller clips in the Projects browser w/o having the larger files still loaded?

I have sucessfully imported 150 Sony digital 8mm movies (each one hour in length) into iMovie as 150 iMovie events. I have since successfully converted them from their original 13 Gb (.dv) file to an exported smaller 1.3 Gb (.4mv "large file") movie that I am happy with, using the iMovie projects browser. So now I have 150 " .4mv" movies on my internal HD as well as about half of my original raw data " .dv " movies on my internal hard drive.
Due to their large size (over 2 Tb), I do not have all the larger raw data (.dv) files on my 2Tb internal drive, just about half of them. What I want to do now is to create a new project in the Projects browser for each of my kids, and reload, starting with Tape #1, each of these larger files and do a highlights movie for each of my kids, wherein I pick out smaller clips from each 1 hour .dv iMovie event and paste them into the appropriate kid's Highlights project in the Projects browser.
Here's my question: If I load the first 5 large files back onto my internal HD, and paste in various shorter clips into each of my kids' Highlights project, and then if I delete those first 5 large files (they are backed up on 2 other 3Tb external HDs), can I keep doing this (reloading the next 5 large .dv files to work with), and ultimately take each of my kid's Highlights project and export as a .4mv movie EVEN THOUGH the earlier large .dv files are no longer on my internal HD, OR does my iMac need to have all these larger files loaded on my internal HD for me to eventually export each of my kid's Highlights project to a .4mv movie?
I have a 2011 era 27" iMac desktop w 2Tb HD internal and 250 Gb flash drive, and Lion OSX and iMovie 11.

Thanks. I tested it out and you were correct. I loaded 2 .dv movies from my external HD back onto my internal HD, and got them re-imported into iMovie, took a few short clips from each of the 2 iMovie events and pasted them into a new project in the Project Browser. Then I deleted these 2 "source clips" from my internal HD, closed iMovie and then re-opened it and found that iMovie would NOT export the smaller clips for a "highlights" .4mv movie without the "source clips" being available.
I read your link on Quicktime. It talks about mostly trimming, which is what I did with each iMovie event before I took each one as a project to export as a smaller .4mv file. But if I use Quicktime (do I need QT Pro or basic), what advantage is it to me to use QT over iMovie (I must admit I am a novice at iMovie and have never used QT or QT Pro as a tool)? Will it then convert any edits I make to a .m4v movie or do I need iMovie to do that?
Does QT allow trimming multiple segments out of a movie during one edit session, or can you only do 1 at a time? By that I mean that, for example, when I use Sonys Picture Motion Browser for my .mts movies, you can only set one Start and one End point for each edit/trim you do: it does not allow you to set multiple Start Stop points like iMovie allows in its Event or Project browser. You can only do one "trim" at a time, save it and then reopen to do another trim. not very useful.

Adobe Premiere Elements 7.0 hangs while exporting and during peak file generation.

I have Adobe Premiere Elements 7.0 (PRE7). I have a project which is using a single clip from a Mini-DV that was captured with Nero 8. Nero 8 was used because it was captured prior to installing PRE7. The file is 12GB and is on a USB disk drive because I don't have the space on my main hard drive (I have about 11GB free). My project doesn't do too much that's fancy. It merely uses about 20 minutes of the 60 minute Mini-DV captured AVI, and it uses simple transitions between each scene. I also have very simple titles at start and end. No themes or anything else.
I've seen two problems. 1) While editing the project, seemingly (but I'm not positive it's related) while the peek file was being generated, PRE7 would get into a state of using about 40% to 50% CPU, and it would not let me do anything else. The other problem, 2) While using "Share" to export the video to WMA for playback on PC (about 180MB estimated file size according to Adobe), the file is exported to about the last remaining 5 seconds, but then PRE7 goes into that mode of hanging with 40% to 50% CPU usage.
One time when it had this 50% CPU issue, I let it sit overnight, and the export was finished in the morning. The export that time was to a 90MB FLV for posting to the "web" according to the Share wizard. But when I was doing the above (issue #2), it went into the 50% CPU usage but didn't finish after waiting around 2 hours. Even if I were to let it sit that time, and it were to finish, it seems like something's wrong and that this is unacceptable.
When this happens, and PRE7 goes into 50% CPU utilization, there is no pacifier or percentage bar advancing. It usually happens near 100% finished. Only one time did it complete successfully after leaving it unattended at 90% complete for an extraordinary amount of time.
To recap:
C:\ hard drive ---> PRE7, my project.
E:\ USB drive ---> 12GB source AVI file and destination for export.
I saw elsewhere on this forum that someone imported a mini-dv captured AVI into Window Movie Maker and then exported it to Mini-DV from that app. This solved that person's problem with hanging during peak file creation. I had the 50% hang issue during peak file generation but I'm not sure it was related to peak file generation. A peak file was generated in a project which, when exported with share as mentioned above, still did the hang 50% CPU issue. Regardless, I will try the import/export/movemaker thing and report back but I've been trying enough things that I wanted to take a second to ask for assistance.
Does anyone have this issue, and is there a patch or fix?
I might be able to provide a user mode dump of the 50% CPU adobe process. There is some call stack information and I'm wondering if developers would want this info if they don't already have a solution/fix to this bug.
Thanks for any help.

I have some more info on the hang which I've been experiencing during export/share of a project which uses an AVI as its one main clip. Adobe Premiere Elements 7 (PRE7) appears to be hanging because it's looping endlessly in ImporterAVI.prm. I'm wondering if this info can be passed onto Adobe developers and/or if I can submit this information elsewhere for such processing. I also have a process dump file which might be helpful, not to mention the original project files.
I used Process Monitor to help analyze this situation, and prior to PRE7 getting into the endless loop, it appears to be reading from the AVI file little by little, and WMEncodingHelper.exe is writing out little by little to the destination file, both of which I would expect. When PRE7 gets to the end of the import/export, Process Monitor appears to show all the aforementioned disk activity ceasing. I see neither process reading or writing. This would be normal if the share/export procedure had completed. But PRE7 is not complete. It is hung and is operating at 50% CPU utilization.
Far below in this post are technical details which may be helpful to an Adobe developer determine why the importer could get into this endless loop. In those details, there is a jump instruction, "jb ImporterAVI!xImportEntry+0xf32", which will always jump if a particular compare always turns out a certain way. But in my review of the counters being compared, it never will get to a point of exiting. When I modify a flag (the carry flag) to be 0, the loop exits. When I did this, my export/share of my project completed successfully. So it was done, but for some reason, PRE7 was looping and looping in its AVI importor instead of completing the export (aka "Share").
I cannot say that this certainly indicates a bug with PRE7, but it seems to me that there's enough data for Adobe to be at least investigating this particular issue. I'm not the only person who has seen this as there was at least one other message describing the same problem which the user resolved by effectively re-creating the AVI file via a no-op import/export into and out of MovieMaker. My AVI also goes through MovieMaker, import/export, without a hitch.
In a sense, I view PRE7's "share" as essentially an import, processing of imported information (i.e., effects and transitions), and an export. It's an import of all clips into the project at the right times, a processing of all effects, and finally an export to a destination. I realize this is simplistic, but the point I'm making is I have a simple project with a single AVI, and it appears that the "import" portion of PRE7's Share option is choking on the only clip used by this project. I also don't have much but simple transitions and a beginning/ending title on the project, so I'm not thinking this use of PRE7 is much more than what I'm doing with MovieMaker when importing/exporting this AVI.
I fully agree that optimum hardware can be either required or critical for certain types of video editing, but PRE7 is a consumer program and I'm not using anything extensive about it and the symptoms are that PRE7 is looping on its import of a file other programs don't have a problem with. I already tried purchasing a 1TB external, which I'm glad I did, but I really think Adobe developers should look at this issue. There may be a problem with handling certain AVI clips used in a project when those clips come from certain sources. If there is an issue, perhaps it could warrant a fix that would make PRE7 more compatible with these other clips.
Does Adobe have a procedure for people to upload (or mail) projects and files to it so that they can troubleshoot why the importer gets into this state? I also mentioned earlier that I have a full user-mode dump of the process which may be of value to a dev. Can I submit this information anywhere?
Here are textual technical details:
Plug-in which loops: C:\Program Files\Adobe\Adobe Premiere Elements 7.0\Plug-ins\en_US\ImporterAVI.prm
The following are the instructions at the "bottom" of the loop which never ends. Below, I put "***" at the jump instruction I mentioned earler. If I force the carry flag to be 0 at that point, and the jump is skipped, the export completed successfully. Additionally, notice that [esp-0x1c] is 0x2000, and that both eax and edi are 0. When I see it loop, eax stays at 0 and never reaches 0x2000. I wonder if something about the AVI is causing values used by this importer to be such that it causes this endless loop, and if that's the case, and if such values are valid/good, I'm wondering if the importer can be fixed by being able to detect such values so as to not choke (if in fact it's an importer issue).
1239dda2 50 push eax
1239dda3 ffd1 call ecx
1239dda5 8b442424 mov eax,dword ptr [esp+24h]
1239dda9 015c2428 add dword ptr [esp+28h],ebx
1239ddad 03c7 add eax,edi
1239ddaf 83c410 add esp,10h
1239ddb2 3b44241c cmp eax,dword ptr [esp+1Ch]
1239ddb6 89442414 mov dword ptr [esp+14h],eax
; *** This is where it loops around and around.
1239ddba 0f82f2feffff jb ImporterAVI!xImportEntry+0xf32 (1239dcb2)
ImporterAVI!xImportEntry+0x1040:
1239ddc0 8b542420 mov edx,dword ptr [esp+20h]
1239ddc4 52 push edx
1239ddc5 e810d40000 call ImporterAVI!xImportEntry+0xe45a (123ab1da)
1239ddca 83c404 add esp,4
ImporterAVI!xImportEntry+0x104d:
1239ddcd 5f pop edi
1239ddce 5e pop esi
1239ddcf 5d pop ebp
1239ddd0 33c0 xor eax,eax
1239ddd2 5b pop ebx
1239ddd3 83c428 add esp,28h
1239ddd6 c3 ret
ChildEBP RetAddr Args to Child
WARNING: Stack unwind information not available. Following frames may be wrong.
3195d9b8 12387545 10590f9c 27c53e00 06b35ff6 ImporterAVI!xImportEntry+0x103a
3195d9ec 1239ea10 06b35ff6 00000000 27ad8a60 ImporterAVI+0x7545
3195da1c 1238aa31 06b3554b 00000000 7fdf0000 ImporterAVI!xImportEntry+0x1c90
00000000 00000000 00000000 00000000 00000000 ImporterAVI+0xaa31
[esp-1Ch]: 3195d9a0 00002000
eax=00000000 ebx=00000000 ecx=3195dbcc edx=00000000 esi=27ad8a60 edi=00000000
eip=1239ddba esp=3195d984 ebp=3c7ba50b iopl=0 nv up ei ng nz na pe cy
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000287
ImporterAVI!xImportEntry+0x103a:
1239ddba 0f82f2feffff jb ImporterAVI!xImportEntry+0xf32 (1239dcb2) [br=1]

CS6 hang during file save on mac OSX 10.6.8

Experienced several occurances of Photoshop CS6 file save hang during background file save and autosave on mac OSX 10.6.8.
The file save percentage counter initially showed progress, but then just stopped.
Close window and quit application commands were blocked by the background save.
Other editing commands commands were still possible.
The files were large .psb files (>2Gb)
Unfortunately no dump available as application was terminated with force quit.
No problems experienced with these files under CS5.

Experienced several occurances of Photoshop CS6 file save hang during background file save and autosave on mac OSX 10.6.8.
The file save percentage counter initially showed progress, but then just stopped.
Close window and quit application commands were blocked by the background save.
Other editing commands commands were still possible.
The files were large .psb files (>2Gb)
Unfortunately no dump available as application was terminated with force quit.
No problems experienced with these files under CS5.

P45 Neo2-FR hangs during large file moves

Similar Messages

Maybe you are looking for