When I try to open an image or a subfolder while the browser is being updated - the status bar "Updating browser information" is running, the PWP 7.0.11 Pro 64 bit crashes. Repeated several times with the same result, no other application is running on the PC at the same time. Can anyone confirm on a similar or a different configuration?
Win 7 Professional 64 bit SP1 on Intel Core(TM)2 Quad CPU Q8300 2,5 GHz, RAM 4 GB
Thanks,
David
Updating browser information problem
Moderator: jsachs
-
Dieter Mayr
- Posts: 453
- Joined: April 24th, 2009, 11:47 am
- What is the make/model of your primary camera?: Nikon D700
- Location: Salzburg / Austria
Re: Updating browser information problem
David, no such problems here with PWP 7.0.11 under Win7 Home Premium SP1. Quad core AMP processor with 2.3GHz and 12 GB RAM.
I have had a problem with updating the browser a while ago, the problem was a corrupted .browseinfo file.
In case you don't know, these are the files where PWP saves all the browser related stuff, thumbnails etc, one such file exists in every folder you have ever browsed.
Try to delete the .browseinfo file in the affected folders and open that folder in PWP again.
This will force the creation of a new .browseinfo file.
Hope it helps
Dieter
I have had a problem with updating the browser a while ago, the problem was a corrupted .browseinfo file.
In case you don't know, these are the files where PWP saves all the browser related stuff, thumbnails etc, one such file exists in every folder you have ever browsed.
Try to delete the .browseinfo file in the affected folders and open that folder in PWP again.
This will force the creation of a new .browseinfo file.
Hope it helps
Dieter
Dieter Mayr
Re: Updating browser information problem
Dieter, I do not think the problem is with the corrupted .browseinfo file. When I wait until the browseinfo file has been updated, there is no problem to open images. The problem is trying to open an image in the middle of the process of updating the .browseinfo file.
The cause might be when the browseinfo file is being updated just after an image of 80-90 MB or more has been saved, so perhaps 4GB of RAM is just not enough, compared to yours 12GB, for this kind of operation. The size of image or contents of a subfolder being opened makes no change, since even opening an empty subfolder causes the crash.
The easy way to simulate it just copy and save an image big enough to have enough time to double-click on another in the browser while the browseinfo file is still being updated.
Anyway, the solution is simple, I just wait until the updating finishes, so it seems to be more of a question about sufficient HW to me then a real problem.
David
The cause might be when the browseinfo file is being updated just after an image of 80-90 MB or more has been saved, so perhaps 4GB of RAM is just not enough, compared to yours 12GB, for this kind of operation. The size of image or contents of a subfolder being opened makes no change, since even opening an empty subfolder causes the crash.
The easy way to simulate it just copy and save an image big enough to have enough time to double-click on another in the browser while the browseinfo file is still being updated.
Anyway, the solution is simple, I just wait until the updating finishes, so it seems to be more of a question about sufficient HW to me then a real problem.
David