search

aata / mplayerx

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

First start will crash #75

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
don't know why
0.9.7 and 0.9.8 both

Original issue reported on code.google.com by cove...@gmail.com on 14 Mar 2010 at 6:20

GoogleCodeExporter commented 9 years ago 
sorry I can't reproduce this problem.

would you please provide some details.

Original comment by zongyao.qu on 14 Mar 2010 at 7:00

GoogleCodeExporter commented 9 years ago 
can crash log help？

Original comment by cove...@gmail.com on 14 Mar 2010 at 8:43

Attachments:

GoogleCodeExporter commented 9 years ago 
Thanks coverno, the crash log helps greatly to figure out where it crashed.

But now I don't know the reason, it crashes when setting up the OpenGL 
environment, 
which I didn't interrupt but just let the default behavior go.

It could be Apple's bug, but I will investigate further.

at this point, I still need some information.

Since it is about the OpenGL, 
1. would you please tell me the details about your Mac, such as the vender of 
the 
video card, the size of the video ram,,,?

2. Does it, almost, only crashes for the first time, or it crashes continually?

Original comment by zongyao.qu on 15 Mar 2010 at 1:10

GoogleCodeExporter commented 9 years ago 
thx bro.
1,
2，it only crashes for the first time

Original comment by cove...@gmail.com on 15 Mar 2010 at 3:20

Attachments:

GoogleCodeExporter commented 9 years ago 
I am seeing this crash also, June 2009, Macbook Pro 17-inch.

Original comment by joe.roback@gmail.com on 27 Mar 2010 at 1:56

Attachments:

GoogleCodeExporter commented 9 years ago 
I also seen a different crash, also at startup.

Original comment by joe.roback@gmail.com on 27 Mar 2010 at 1:57

Attachments:

GoogleCodeExporter commented 9 years ago 
this may not be the true reason that the app crashes:

The default implementation when choosing the pixel format to set up the OpenGL 
environment, has NoRecovery, which means there is no fallback to a compatible 
pixel format if failed to get the pixel format 
which the app wants.

But I can't explain why this only happens for the very first time,~~~

and I am not sure to delete NoRecovery will fix it, since I have never 
encountered such problem.

Original comment by zongyao.qu on 27 Mar 2010 at 8:21

GoogleCodeExporter commented 9 years ago 
oops, also met this problem after updated to 10.6.3

and only the first time

Original comment by zongyao.qu on 29 Mar 2010 at 9:58

GoogleCodeExporter commented 9 years ago 
Seems someone is struggling with this too, from 2009-12

http://lists.apple.com/archives/quartzcomposer-dev/2009/Dec/msg00075.html

And after reading that, it is probably the OS bug.

Original comment by zongyao.qu on 30 Mar 2010 at 1:56

GoogleCodeExporter commented 9 years ago

Original comment by zongyao.qu on 30 Mar 2010 at 1:57