Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MME 1.3.3: Crash when using double calculate sign #1179

Closed
2 of 6 tasks
ffoknissom opened this issue Jun 5, 2017 · 6 comments
Closed
2 of 6 tasks

MME 1.3.3: Crash when using double calculate sign #1179

ffoknissom opened this issue Jun 5, 2017 · 6 comments
Labels
bug outdated related to old version, already changed win related to Windows pltform

Comments

@ffoknissom
Copy link

ffoknissom commented Jun 5, 2017

  • Check OS
    • Windows 10 64bit
    • Mac OSX
    • Linux
  • Check MMEX version
    • 1.3.3
    • 1.2.x
    • 1.1 or older

When making a new transaction and using double calculate signs (like --, ++, ::, xx) in the Amount box (e.g. 100--50) the program crashes after clicking OK

mme_crash_01

@vomikan vomikan added the bug label Jun 11, 2017
@stef145g
Copy link
Contributor

I have tried this in Win 10 and Win 7 and could not reproduce problem.
Putting an amount 100--50 produced a warning message that this was invalid.

@ffoknissom
Copy link
Author

Good morning Stefano,
It only occurs in 64 bits, i just tested in 32 bits and a warning message appears. Hope that helps!

@stef145g
Copy link
Contributor

Both machines tested on are 64bit.
Win 10 Home version 1607 build 14393.693 (Having update problems)
Win7 Home Premium editions.

@ffoknissom
Copy link
Author

Tested just now on my work on a Windows 8.1 Enterprise machine (64 bits). Fresh download from Sourceforge, both 32 bits and 64 bits MMEX 1.3.3 portable packages, same packages i use at home.

Same thing happens, the 32 bits version works fine and generates a notification, the 64 bits version crashes immediately after hitting the ENTER key or click on OK button.

@stef145g
Copy link
Contributor

I have now downloaded the 65Kbit package from Sourceforge.net and I get the same result as you. I had been testing the versions I had built at that version and beyond. This is the reason I could not find the problem initially. This mean that something went wrong in that specific build.

@ffoknissom
Copy link
Author

Ah oke, that makes sense. Now i know i'm not seeing ghosts :)

@slodki slodki added the win related to Windows pltform label Jul 22, 2017
@vomikan vomikan added invalid outdated related to old version, already changed labels Mar 20, 2018
@vomikan vomikan closed this as completed Mar 20, 2018
@slodki slodki removed the invalid label Mar 21, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug outdated related to old version, already changed win related to Windows pltform
Projects
None yet
Development

No branches or pull requests

4 participants