search

k-kawa / aseprite

Automatically exported from code.google.com/p/aseprite
0 stars 0 forks source link

OSX Lion crash #92

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. *****$ ./aseprite 

What is the expected output? What do you see instead?

It closes the program immediately!
Everything else seams ok with the OS.
Check the terminal messages at the end.
Thanks!

What version of the product are you using? On what operating system?

OSX Lion

aseprite
v0.9.1

Please provide any additional information below.

$ ./aseprite 
2012-04-02 17:11:49.017 aseprite[2425:5107] Warning once: This application, or 
a library it uses, is using NSQuickDrawView, which has been deprecated. Apps 
should cease use of QuickDraw and move to Quartz.
aseprite(2425,0xac6432c0) malloc: *** error for object 0x58c1a0: pointer being 
freed was not allocated
*** set a breakpoint in malloc_error_break to debug
Shutting down Allegro due to signal #11
Segmentation fault: 11

Original issue reported on code.google.com by machado....@gmail.com on 2 Apr 2012 at 4:16

GoogleCodeExporter commented 8 years ago 
I've tried redownloading the program several times and it closes immediately. I 
get the message that it has closed unexpectedly and asks for me to report it to 
Apple Automatically. I'm running OS X Version 10.6.8 with ASEprite Version 
0.9.1.

Original comment by TechnoRe...@gmail.com on 27 Apr 2012 at 1:35

GoogleCodeExporter commented 8 years ago 
TechnoRezou: Are you using aseprite 0.9.1 or 0.9? Because 0.9.1 is not yet 
available for Mac OS X (only if you've compiled it by your self).

Original comment by davidcapello on 27 Apr 2012 at 1:43

GoogleCodeExporter commented 8 years ago 
I was mistaken, it was 0.9. (ASEPRITE 0.9 for Mac OS X (Thanks to Jamaal 
Sawyer)) No Compiling done at all, just a straight download and run attempt.

Original comment by TechnoRe...@gmail.com on 27 Apr 2012 at 1:57

GoogleCodeExporter commented 8 years ago 
I've got the same problem with ASEPRITE 0.9 for Mac, running os X Lion 10.7.3. 
It quits unexpectedly right after launching. An empty window is visible for a 
very brief moment. I tried to run ASEPRITE via the Terminal going directly into 
aseprite.app/Contents/MacOS/aseprite and produces the same result, but with an 
additional error message, saying: 

aseprite[3383:510b] Warning once: This application, or a library it uses, is 
using NSQuickDrawView, which has been deprecated. Apps should cease use of 
QuickDraw and move to Quartz.
objc[3383]: nil: message release sent to freed object=0x52ae10
Illegal instruction: 4

Any chance of fixing this? I tried ASEPRITE on a wintel pc and I'd love to use 
it on my Mac.

Original comment by orth.marcoliver@gmail.com on 3 May 2012 at 3:42

GoogleCodeExporter commented 8 years ago 
Just wanted to say I've been experiencing this issue as well, though I have a 
theory as to its cause.

I've managed to launch aseprite successfully on my Mac a single time, at which 
time it was connected to an external monitor. I suspect that the fact I've 
tried to launch it without that monitor present has something to do with this 
crash.

Anyhow, I'm on OS X 10.7.5 with Aseprite 0.9.5, and this is the error I'm 
seeing when launching aseprite from the command line:

2013-03-26 10:03:12.771 aseprite[59039:6507] Warning once: This application, or 
a library it uses, is using NSQuickDrawView, which has been deprecated. Apps 
should cease use of QuickDraw and move to Quartz.
aseprite(59039,0xace852c0) malloc: *** error for object 0x189ab00: pointer 
being freed was not allocated
*** set a breakpoint in malloc_error_break to debug
Shutting down Allegro due to signal #11
[1]    59039 segmentation fault  ./aseprite

Original comment by HolyEggp...@gmail.com on 26 Mar 2013 at 5:32

GoogleCodeExporter commented 8 years ago 
For anyone coming across this, I just tried killing my .asepriterc file and 
launching again. Worked like a charm.

Original comment by HolyEggp...@gmail.com on 27 Mar 2013 at 8:50

GoogleCodeExporter commented 8 years ago

Original comment by davidcapello on 29 Mar 2013 at 5:50

GoogleCodeExporter commented 8 years ago

Original comment by davidcapello on 29 Mar 2013 at 5:50

GoogleCodeExporter commented 8 years ago

Original comment by davidcapello on 10 Apr 2014 at 1:06

GoogleCodeExporter commented 8 years ago

Original comment by davidcapello on 10 Apr 2014 at 1:09

GoogleCodeExporter commented 8 years ago 
It was an old problem with deleted directories in recent files (or last used 
directory). Anyway it shouldn't happen in v1.0 anymore.

Original comment by davidcapello on 15 Jun 2014 at 8:19