Guide bug - can you reproduce it?

[Montwerx]

Guide bug fixed in update to version 13.2.0.35.
I just put 15 guides Vertical and 15 horizontal and no problem at all. Last night it was crashing me. Cool beans!
Thanks, Corel team!

[jaxman]

Sorry, I'll have to disagree that this guide bug has been fixed, at least on a Windows Vista system. I can still re-create this problem 100% of the time with the latest patch installed. Program goes into "not responding" mode and has to be aborted manually, and CPU usage is at 100%.

No thanks (yet) to Corel.

[LeviFiction]

Well we Windows 7 users can thank them. Haha. Try contacting Corel to see if they can't be given more information on the systems where this problem occurs. Might help.

[Ron P.]

The only way I can get it to crash, is by shaking one of the guides so violently that it is hard to keep it on the stage. Otherwise I can stuff so many guides vertical and horizontally that you can barely see the stage, and still no crash.

[marty2010]

No problems observed using guides (moving/pausing/moving/normal moving operations) with Patch #2 installed.

Memory usage normal.

CPU usage goes to about 29% while moving the guides around.

CPU then drops to 2% when not moving the guides.

[Corelistani]

well, since everyone's interested in this topic, i'll have to add my input. i've never been able to crash the program wiggling the guides about. no hangs either. i have a quad core system and my results concur pretty much with marty2010 cept most of the usage activity is in my 3rd core (33%) instead of his 4th. i'm on an XP Pro SP2, upgraded PSPP X3 to 13.2.0.35 with the latest patch.

[LeviFiction]

One quick thing.

While the initial problem reported on the YouTube video states that it needs to be wiggled it was later discovered that simply holding the guide for too long without dropping it was what was happening. Also the length of time that a person needs to hold onto the guide when first created is different from person to person. Some it's almost right away, others it takes a prolonged time. If you drop the guide on the image you can move it around afterward without any problems.

So if you experience this problem, especially with patch 2, contact support to see if they can't further narrow down this problem. It's fixed on my end so it means they fixed something but if more fixing is needed they are still working on the other problems and so it'll probably improve as more people contact them about a single problem.

[df]

I just tried it on my Vista machine and no crashing. I tried 9 vertical and 9 horizontal guides. I held one, then jiggled till I was almost off the page, solid. Didn't look into CPU usage though.

[markcrisell]

Windows 7 user here, patched to the recent update, very easy for me to get this bug to reproduce.

Will raise with support.

[[Mike]]

Hello there,

Finally decided to sign up, never had any problems with X2, but with X3, oh my... Have several support threads running, among others, one about the guide bug.

Came here today to look for news about a possible update (purchased and ran 13.0.0.264), I have just installed 13.2.0.35 and on my first try I locked up PSP real nice. Only had to hold a vertical guide for about 4 to 5 seconds... So yeah, it ain't fixed (completely).



Will (re)open a support thread.

[-DJ-]

Whoa, first time I'd heard about this bug so just tried it...yep, takes about 4 seconds to blow PSP out of the water (this is with X3 patch 2 installed on Vista x64)

[[Mike]]

Okay, so I reopened a support thread. My last and first thread about the Guide Bug contained the following: "The issue with the guides has already been logged and may also be fixed in a product update. At the moment the only workaround is to place the guides quickly.".

In the new thread I said: "I have just updated to 13.2.0.35 and the guide bug remains. I will help you any way I can to get this fixed, but I refuse to spend money on that process, so please don't copy and paste any phone numbers. Thanks.".

Corel's response: "Thank you very much for your e-mail.

To further assist you on your concern, can you please provide me more information regarding your concern?

Please do not hesitate to contact us for any further questions."

[LeviFiction]

So we need to report it personally. On it. Technically the money is only for how-tos not for reporting bugs. So calling them has never cost me a cent, even though I have two support tickets that I can use they haven't required them at all. I'll go ahead and call as well, point them to this topic post. It'll get sorted out.

[[Mike]]

Well, I'm not sure how it works, had a bit of a discussion about it in another support thread, but if they give me a phone number in the US or UK or whatever, I'm pretty sure my phone company is gonna charge me for the call. Irregardless of what Corel may or may not charge me. And I'm not that confident that I'll get it explained in a minute, so I'm not going there. Well, I can explain it in a minute, but will they get it in a minute... So I'm not spending one additional cent on this, bad enough I have to spend this much time and effort on it.



Anyway, any help is appreciated!

[LeviFiction]

Yeah they probably won't get it in a minute. But for a very good reason, assuming you get a competent support rep.

1800 numbers tend to be toll free, but unless they say it I wouldn't do it.

I almost never use my cell-phone so I just use my regular minutes. So here's what happened when I called.

First he had me walk him through the steps to create the bug and can verify that it does still happen. He had me give him specifics from my DirectX Diagnostics program, and from Windows Event logs on the error. Which kind of had me scared because I reported above that the guide problem is gone. It's not gone. It just didn't crash my program the first five times I tried it. So I was able to send the event logs. He's including his own event logs from his test systems.

And he is reporting the problem. It'll be of more use to the engineers to get such information from other people, so if you can afford the minutes from your phone company my suggestion is to call and hopefully they'll all request the same information and the engineers can get a clear picture on what's causing it.

So it has been reported, and they are going to look at it. Frustrating though it may be it seems the phone gets the best results.