Runtime Error

[bruce1951]

I'm getting a runtime error. 'R6025 - pure virtual function call'.

This has happened a few times. PLD file. I have a cutout/contour layer. I select the layer and Filters/External program. (I want to send the object to PSPx8). Get the usual message asking about layer etc. Then the error message. But it still sends the object to PSP. I hit OK and get a message that PL has stopped working. Of coarse I've lost my file in PL because it has closed.

Any clues what is happening?

regards

[Martin Huber]

I'm getting a runtime error. 'R6025 - pure virtual function call'.

This has happened a few times. PLD file. I have a cutout/contour layer.

So your document is:
- background layer
- vector-based clipping layer
?
What are the specs of the background layer (8 or 16 bit, color space, size)? Has the document a ICC color profile? Has the document meta data?

A small sample document to reproduce the problem would be helpful.

I select the layer and Filters/External program. (I want to send the object to PSPx8). Get the usual message asking about layer etc.

What option do you select? What file format is used for transferring the data?[/quote]

Martin

[bruce1951]

Martin I'm not to tech savy so be gentle with me!!

I open PL and load a 136meg tiff. 300dpi. 5986*3992. RGB. 16 bit.
Duplicate the layer. Then save as a PL file. Select the top layer. Then Filter/External Programs/CorelPaintShopPro. Select Edit Active Layer. All's fine so far. (I use PSPx8 to cutout an object. I simply feel more comfortable using PSP rather than doing it in PL. Old dog new tricks!!!).
Now because PSP has issues saving tiff/transparencies I save my edit, in PSP, as a PNG file.
Close the file in PSP.
Return to PL. Open the saved PNG file. Copy. Then paste that copy as a new layer on my working file. So far all is good.
Now if for some reason I wish to send that layer back to PSP. Back to Filter/External Programs/CorelPaintShopPro. Select Edit Active Layer. Here is where I get the Runtime error. 'R6025 - pure virtual function call'. Not always. About 1 in 5 or 1 in 6 times.

It's not an issue I can deliberately reproduce. It's a random issue. It makes me wary as if this happens PL stops running and work is lost. Now before I go to the external editor I do a save. Just in case. If PL stops working all I have to do is open PL, load the file and continue on.

My concern is 1/is it something I'm doing? 2/is it a system issue? or 3/ is it a PL issue?
I have a work around but one day I'll forget and I tend to swear a lot!!!!!!!!

regards

[photoken]

I open PL and load a 136meg tiff. 300dpi. 5986*3992. RGB. 16 bit.
Duplicate the layer. Then save as a PL file. Select the top layer. Then Filter/External Programs/CorelPaintShopPro. Select Edit Active Layer.

What file format are you using to transfer the PL Layer to PSP?

Your workflow sounds to me that you should be using PNG right from the get-go to send the Layer to PSP....

(By the way, PL's "Edit Active Layer" is a "live" function -- as long as you keep the image open in PSP, any edits you do in PSP and save are immediately updated in PL.)

[bruce1951]

Ken I've used the same method for a lot of photos and only just recently had the runtime issue.
I'm aware that the layer in PSP is 'live'.

The simple fact is that I treat PSP as just another plugin. There are some compatibility issue and I have work arounds. Mostly has to do with transparencies and tiff/png combinations.

regards

[bruce1951]

Any ideas?
I'm still getting the 'Microsoft Visual C++ Runtime Library error.
R6025 - pure virtual function call.

It happens when using the External Editor.

If I haven't save in a while then I loose my work.

Happens about every 6 - 10 times I use the external editor.

The file still goes to PSPx8. But PL will stop running. (Photoline as stopped running. Close? OK). In PSP I continue on and do a save as, png file. I can then open that file in PL once I restart it. How ever PL can be very slow. The next save and consequence saves can take a minute or two. As a png. Canceling the save doesn't work either. If I try then I finally get a message saying the file can't be saved. If I do a save as and change to tiff then everything is back to normal!!

regards

[photoken]

Hi Bruce,

In addition to the information that Martin requested, the next time you get that error, take a look at the Windows Event Logs to see if they have anything useful in them.

I know you're running Windows 8.1, but if you type
event log
in the Windows Search box, you should get an option to view the event logs. When the Event Viewer app opens, expand the "Windows Logs" folder and look at the "Application" log. By selecting an event with the red "error" icon, you'll see a description of it which you can copy & paste into a message.

Look at all the error events -- you might have one for PhotoLine, and another for PSP....

[bruce1951]

OK is this what you were looking for?

Log Name: Application
Source: Application Error
Date: 8/22/2016 10:38:45 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: myHP
Description:
Faulting application name: PhotoLine64.exe, version: 19.5.0.0, time stamp: 0x56e13577
Faulting module name: PhotoLine64.exe, version: 19.5.0.0, time stamp: 0x56e13577
Exception code: 0x40000015
Fault offset: 0x000000000056c9e0
Faulting process id: 0x1434
Faulting application start time: 0x01d1fcf55176c4f5
Faulting application path: C:\Program Files\PhotoLine\PhotoLine64.exe
Faulting module path: C:\Program Files\PhotoLine\PhotoLine64.exe
Report Id: 7928cf04-68eb-11e6-8284-6cc21767dc92
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2016-08-23T04:38:45.000000000Z" />
<EventRecordID>38212</EventRecordID>
<Channel>Application</Channel>
<Computer>myHP</Computer>
<Security />
</System>
<EventData>
<Data>PhotoLine64.exe</Data>
<Data>19.5.0.0</Data>
<Data>56e13577</Data>
<Data>PhotoLine64.exe</Data>
<Data>19.5.0.0</Data>
<Data>56e13577</Data>
<Data>40000015</Data>
<Data>000000000056c9e0</Data>
<Data>1434</Data>
<Data>01d1fcf55176c4f5</Data>
<Data>C:\Program Files\PhotoLine\PhotoLine64.exe</Data>
<Data>C:\Program Files\PhotoLine\PhotoLine64.exe</Data>
<Data>7928cf04-68eb-11e6-8284-6cc21767dc92</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>

[photoken]

Yeah.

It doesn't show anything that is meaningful to me....

Was there any error from PSP?

[photoken]

Also, that version of PL should be 19.5.1.0. Are you using the latest version?

[bruce1951]

Ken I only update every now and again. Unless there is a great jump in features/improvements I don't bother. PSP acted 'normal'.

regards

[photoken]

Bruce, I used to be the Senior Technical Consultant for a small software company that sold client/server database applications to corporations. The first and foremost thing all our tech support personnel were taught when dealing with our customer's problems was to ensure that the customer was running the current version of our software. That's the only way the developers could troubleshoot reported problems because only the current version contained the code that addressed both the problems that were experienced by our customers and the problems that had not yet been reported.

Just about every time a new version of an application is released, there are changes to the code that are never mentioned in the "What's New" documentation. Often, that's because the code addresses issues that had not been discovered by the customers; or because the changes are way too technical to make sense to the general public.

The PL numbering scheme of "19.51" leads me to believe that something was discovered in version 19.50 that required a fast replacement of the program....

[bruce1951]

Well you have 'embarrassed' me into downloading the newest version.
Good thing PL is such a small download.

regards

[photoken]

Good thing PL is such a small download

Amen, brother.

[bruce1951]

Ken a long time ago, years and years ago in fact, I studied for a certificate, a diploma and a degree. Majoring in data processing, programming and systems analysis. (As well as business law, accounting etc). You would think I'm up with all the latest 'stuff'. On the contrary. Long ago I learned not to 'fiddle' with computers and programs. As a result I don't 'modify' computers. 'Play' with settings. Or up date software without good reason. The thing is I know all to well the dangers of straying off the path. 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!! Am I paranoid? Maybe. Maybe yes. I've simply seen too many folks get into trouble with computers to do the same thing.

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?

regards