Bug #640

Crash during resize

Added by Priv over 3 years ago. Updated about 3 years ago.

Status:AcceptedStart date:11.03.2016
Priority:NormalDue date:
Assignee:-% Done:

90%

Category:-
Target version:3.2.2
Version: Operating System:Windows 7/8/10 64bit

Description

Nomacs crashes when I try to resize an image with Lanczos resampling. It's happening on Windows 7 64bit. I tested it on Linux too and it's working fine there.

Steps to reproduce:
1. Open image
2. Open resize dialog
3. Change resampling method to Lanczos
4. Try to enter new width
5. Nomacs stops responding

Nomacs version: 3.0.0.3000[x64]

img-2016-06-13 09.44.45.png - resize-screenshot (170 KB) Preview Markus, 13.06.2016 09:46

c.webm (1.13 MB) Priv, 16.06.2016 21:29

223

History

#1 Updated by Priv over 3 years ago

Problem signature:
Problem Event Name: APPCRASH
Application Name: nomacs.exe
Application Version: 3.0.0.3000
Application Timestamp: 5672859b
Fault Module Name: opencv_imgproc300.dll
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 56053b78
Exception Code: c000001d
Exception Offset: 00000000009d715a
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 5146
Additional Information 1: 4c0a
Additional Information 2: 4c0a824fd5ef6f16bef792ef9dfe38cd
Additional Information 3: 2816
Additional Information 4: 281611f402f6c558ce2299aebc39c974

#2 Updated by Markus over 3 years ago

  • % Done changed from 0 to 90

hi,

thanks for the report - I cannot reproduce it with the current beta. So I hope this is fixed by now.

regards,
markus

#3 Updated by Markus over 3 years ago

  • Target version set to 3.1

#4 Updated by Priv about 3 years ago

Unfortunately I'm still getting this, even with a fresh Windows 7 64bit install and the latest Nomacs version. The steps to reproduce it are the same.

Problem signature:
Problem Event Name: APPCRASH
Application Name: nomacs.exe
Application Version: 3.2.0.174
Application Timestamp: 5721f6e7
Fault Module Name: opencv_imgproc310.dll
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 56bcb37b
Exception Code: c000001d
Exception Offset: 00000000013711da
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 5146
Additional Information 1: 275b
Additional Information 2: 275b2d3a6dea1b198c5e89c564ecb6fc
Additional Information 3: f6df
Additional Information 4: f6dfeafa5af57e75c42b79cdc7d74c28

#5 Updated by Markus about 3 years ago

  • Status changed from New to Accepted
  • Target version changed from 3.1 to 3.2.2

hi,

that's a pity... could you please send us an image to reproduce it?

#6 Updated by Priv about 3 years ago

Any image triggers it. But I attached a link to a random one which caused it to crash.
I installed a clean (verified hash sum) version of Windows 7 64bit SP1 Media Refresh. Nothing except for Nomacs and a few other unrelated programs is installed. Let me know if you need more info. Meanwhile I'll try to see if I can reproduce this on a different computer with the same OS.

https://www.nasa.gov/sites/default/files/styles/image_card_4x3_ratio/public/thumbnails/image/leisa_christmas_false_color.png?itok=Jxf0IlS4

#7 Updated by Priv about 3 years ago

Okay, I tried it in a virtual machine running Windows 7 and it happened there as well.

#8 Updated by Markus about 3 years ago

I tried it again (now the official nomacs 3.2 portable in a Win7 VM) - see screenshot. Again it did not crash... Is there any setting that you apply prior to changing the size?

#9 Updated by Priv about 3 years ago

Is there any setting that you apply prior to changing the size?

Nothing of the sort. All I did was

- extract Nomacs
- start it
- load an image
- click resize
- change to lanczos resampling
- type in the entry field

I attached a short video of all the steps (running Nomacs 3.2.1 x86_64 installed on actual hardware; Windows 7 64bit).

I tried it again in a VM, both i686 and x86_64 versions of Windows/Nomacs. I also tested both the portable version and regular installer. No matter what I did, it crashed upon resizing with Lanczos resampling.
Could my hardware affect this in any case? Since I'm not really using the Windows version, but the Linux one which works fine, I could write this off as a special "hardware/configuration bug" if no one else can reproduce it.

Also available in: Atom PDF