Runtime Error

[bkh]

Anyway my photo editing computer is now happily running the latest version of PL. So what, may I ask, are the changes from 19.5.0 to 19.5.1?

Just look in the announcement section of the Forum:
http://www.pl32.com/forum3/viewtopic.php?f=6&t=5270
Probably a number of unmentioned bug fixes as well.

Cheers

Burkhard.

[bruce1951]

Sorry folks. New version is doing the same. Runtime error.
When I go to External editor I'm getting the error message. Not always but every 6-10 times.

regards

[photoken]

I have a dedicated photo editing computer that NEVER gets hooked up to the internet. I have an old internet computer. The two never talk to each other!!

I can appreciate that approach. It's the safest (as long as the "old internet computer" is running the latest version of Windows); the Internet can be a very dangerous place, indeed.

Sorry to hear you're still getting the runtime error, but updating PL was worth a try. I'm out of ideas.

I think it's time to email PL support directly on this one, so you can supply a sample image file.

[bruce1951]

Oh dear. I'm getting another hiccup! When I do a save PL disappears. Doesn't close. Just closes the screen. Clicking the PL icon at the bottom of my screen brings it all back again as though nothing happened!!

regards

Ignore the above. My oops. I have a health issue with my right arm. I'm doing things a bit 'different' and discovered it was how I was putting down my pen!!!

[Martin Huber]

Sorry folks. New version is doing the same. Runtime error.
When I go to External editor I'm getting the error message. Not always but every 6-10 times.

I was able to produce a crash now, though it doesn't really fit your description:
- execute an external program in "active layer" mode
- modify the picture in the external program and save it
- activate PhotoLine (PL will update the layer)
- undo the update in PhotoLine with "Edit > Undo"
- activate the still running external program
- modify and save the picture again
- activate PL and it will crash

The crucial point is the undo. Without that there is no crash.
I will fix that.

If you find additional information how to reproduce "your" bug, I am very interested in hearing it. In my opinion from time to time you are doing something, that you aren't doing most of the time (so you are probably doing it by accident). And that's probably the missing step for reproducing your bug.

Martin

[bruce1951]

Thanks Martin. Yes I do a lot of trial and error thus use the Undo a lot. Often flipping back to the external editor.
I will take note of the Undo actions and see if it dove tails with the crashes.

regards

[bruce1951]

Er um arh er hum. Sorry guys but I'm still getting the same Run Time error. Now this one is very simple. Open a 6000*4000 16bit tiff. Multiple applications of the copy brush. "Run time error". OK. Close Program.
File/wok is lost. The strange thing is that when I reopen PL and try to load a file PL is no longer opening the folder that contained my working files.

Now what? Delete PL and do a fresh reinstall?

regards

[Martin Huber]

Er um arh er hum. Sorry guys but I'm still getting the same Run Time error. Now this one is very simple. Open a 6000*4000 16bit tiff. Multiple applications of the copy brush. "Run time error". OK. Close Program.

If I understand you correctly, you open a TIFF, 6000x4000 pixel, 16 bit (RGB? One single layer?). And then you use the copy brush (what settings? brush size?). And after a while PhotoLine crashes.
If so, I can't reproduce this problem.
What version of PhotoLine are you using? 32 oder 64 bit?

Now what? Delete PL and do a fresh reinstall?

This won't fix the problem.

Martin

[bruce1951]

Thanks Martin.
Yes RGB and a single layer.
Copy brush is 35.0 outside 31.0 inside. 100%. All other settings 0.
74% intensity.
Only eraser.
Channels = normal.
I downloaded and installed the latest version of PL last week. v19.51. 64 bit.

When the runtime error appears nothing works until I hit the OK button. Then it jumps straight to the Close Program window. The only option I get is to shut PL down. I can't copy the history or do a screen capture.

I loaded the same file today and repeated the same simple copy/clone actions. PL worked just fine.

I was wondering if it's a 'leftover' issue from previous files/tasks. I use Nik and Topaz plugins as well as PSP as an external editor. I worked on various files for about an hour. Then I got the run time error on the simplest task!!!!

I'll get the pencil out and see if I can remember to jot down my actions.

Bruce

[bruce1951]

Martin I've spent an hour or two on the same file recreating the same results. Using the same techniques. Darned if I can get it to repeat the runtime error. There seems to be no logic to it. I've use Nik and Topaz plugins. Sent the file to and from PSPx8.
I've been saving regularly just incase. But nothing. The times I have been caught I've lost work by not regularly saving. Do you think it may have something to do with not having enough memory/buffer put aside for PL? It's an i5 laptop with 8gig of ram.

regards

[photoken]

I thought this recent article about how much RAM to have is interesting:
http://www.zdnet.com/article/heres-how- ... 9119057645

[Martin Huber]

Martin I've spent an hour or two on the same file recreating the same results. Using the same techniques. Darned if I can get it to repeat the runtime error. There seems to be no logic to it. I've use Nik and Topaz plugins. Sent the file to and from PSPx8.

If it's not some kind of hardware error (which is quite improbable), there has to be a pattern, but it may be difficult to find it.
But it has to be something special, because otherwise other users would have that problem, too.

I've been saving regularly just incase. But nothing. The times I have been caught I've lost work by not regularly saving. Do you think it may have something to do with not having enough memory/buffer put aside for PL? It's an i5 laptop with 8gig of ram.

That should be enough RAM. If you are using the 64 bit version, there shouldn't be a problem anyway, because when RAM runs out, the OS will use the hard disk. And when that happens, you will know it immediately, because PhotoLine will become significantly slower.

Martin

[bruce1951]

Thanks Martin.
Is there away to save the history in a file like an XMP files saves data? Is it even possible? If so imagine the uses that file could have. Not only for finding bugs but also enabling the repeating of steps/actions to replicate 'styles'. Automatic saving every 10-20 steps!! Hmm interesting.

Now someone will tell me it's a;ready possible.

regards

[bruce1951]

Hmmmm. I've done about 60-70 photos since the last Runtime error. Using all my editing 'tricks'. Then wham, Runtime Error. R6025 - pure virtual function call.

I had a 'simple' PL file. Made up of a 2 layers. 6000*4000. Started as 16 bit tiffs. 300dpi. (I had used PSPx8 as an external editor, Nik and Topaz plugins. Erased sections of the top layer).
I saved as a PL file. Left it on screen for an hour while I assessed it. Came back and decided to Flatten layers. Scaled layer to 1500*900. 300dpi. Renamed file and Saved As jpeg. File saved fine. But PL came up with the Runtime Error. When it does this all the history/Undo List disappears. So I can't relay what all the steps were.

On my hard disk I have the PL file and the Jpeg file saved. So that's not an issue this time. But PL stops running and I get the 'Photoline has stopped working' message. Options are 'Check online ...... etc' and 'Close program'. Well my only option is 'Close the program'. And PL closes.

No other software has been used since turning on the computer except for Photomatix and Nikons NX-D. (NX-D to convert 3 NEF's into 3 16 bit tiffs. And Photomatix to tonemap the 3 tiffs into the file I was working on in PL. "Normal' work flow for me).

Now just to check I loaded the PL file again. Followed the exact same steps. Flattened layers. Scaled layer to 1500*900 @ 300dpi. Renamed and saved as jpeg. Everything worked fine. I repeated this several times. Because it was such a simply procedure I was able to remember the steps. So it's a random issue.

This is becoming a pain and makes me very wary of now using PL.

regards