Page 1 of 1
B3: Batch Processing > Add Text crash!
Posted: Sun Feb 01, 2009 11:03 am
by ckit
- Open XnView in Browser mode
- Select 2-3 JPG's
- Add Text, I think any settings will do...
- Click Ok and crash!
Code: Select all
Response: None
Cab Id: 0
Problem signature:
P1: xnview.exe
P2: 1.96.0.0
P3: 497ecad2
P4: ntdll.dll
P5: 6.0.6001.18000
P6: 4791a783
P7: c0000005
P8: 0002f217
P9:
P10:
I also have the Windows Error Report file but it says pretty much the same thing.
Posted: Sun Feb 01, 2009 12:21 pm
by helmut
Hmm, works for me - no crash. But I cannot see any text added.
Posted: Sun Feb 01, 2009 2:29 pm
by Dreamer
Same here, no crash, but no text added - another bug?
ckit - do you meen "add" text" in "Batch Processing"? Because there is no OK button, but I don't know the other way to add text in browser.
Posted: Mon Feb 02, 2009 12:32 am
by ckit
Actually, I know about the text not being added and was going to report that too until this other more serious bug came along.
Dreamer,
Yes, that's what I meant, sorry for the confusion.
Posted: Mon Feb 02, 2009 1:16 am
by ckit
Great, now I can't reproduce it either.
Another random bug for XnView!
Re: B3: Batch Processing > Add Text crash!
Posted: Mon Feb 02, 2009 1:06 pm
by xnview
Can't reproduce...
Re: B3: Batch Processing > Add Text crash!
Posted: Mon Feb 02, 2009 1:24 pm
by helmut
xnview wrote:Can't reproduce...
What about the non-added text?
Re: B3: Batch Processing > Add Text crash!
Posted: Mon Feb 02, 2009 1:49 pm
by xnview
helmut wrote:xnview wrote:Can't reproduce...
What about the non-added text?
non added text?? When you add 'Add text' there is no text by default...
Posted: Mon Feb 02, 2009 2:14 pm
by ckit
No, what we mean is... you should be able to add text "Copyright, ckit 2009" to 9 images via Batch Processing\Add Text but at the moment it seems to be broken.
Posted: Mon Feb 02, 2009 3:36 pm
by xnview
right...
Posted: Tue Feb 10, 2009 9:42 am
by ckit
Fixed in Beta 4 and I'm not seeing any crash either
Posted: Tue Feb 10, 2009 9:58 pm
by Dreamer
Confirmed, fixed in beta 4, thanks, Pierre.
Closed.