Should I write in Flash Professional or Catalyst?
I have Adobe Design Premium CS5. I'm about to write a simple file web based SWF uploader (with chunking). Should I write my uploader in Flash Professional or in Catalyst, in Flash Player or in Flex. I'm confused, heck I do not even know which Adobe forum to post this question to :-(
Can anyone point me to a list of simple heuristics to help me choose between IDEs and SDKs please.
Just do it in Flash CS5.5. Sounds like you have no experience with Flash or you wouldn't be asking this question. There's no point in getting the Flex framework involved. You could use Catalyst to prototype the UI and then use Flash, but I wouldn't bother.
Similar Messages
-
I need Air for desktop application either in .exe or in .air with embedded captive runtime just like .apk . I don't want to install adobe air separate . everything should come in installer
I have adobe flash professional cc development tool , let me know whether I have to go with other development tool???
your reply will increase my confidential level
please anyone can help me to solve this problem
Thanks®ards
NiranjanAdobe Flash Professional CC manual
1) Create new project
2) Configure your Project properties
3) Embed runtime, so you users can use Adobe AIR without pre-installed Adobe AIR runtime
4) After publishing you will receive %APP_NAME%.app folder that contain your project files -
When i'm starting adobe flash professional there is an error 5 what should i do?
When i'm starting adobe flash professional there is an error 5 what should i do?
Can you check the solution mentioned in this thread to see if it helps?
Configuration error 5 (http://forums.adobe.com/thread/628476)
Thanks,
Preran -
I'm a CC member and I've downloaded and installed Adobe Flash Professional CC, but it will not open. How should I proceed?
You can try:
creative cloud desktop failed to install
Downloading and installing desktop apps from Creative Cloud
Problems with Creative Cloud (apps not starting)
Hope it helps you.
Regards
Rajshree -
FAQ: What information should I provide when asking a question on Flash Professional forums?
When asking a question on the Flash Professional user-to-user forums, you can make it easier by proactively providing answers to the following questions:
Have you installed the recent updates? (If not, you should. They fix a lot of problems.)
Please give us more information about your Creative environment:
What version of Flash Professional are you using? And, if applicable, include the minor version number (e.g., Flash Professional CS5.5 with the 10.5.1 update).
What operating system? This should include specific minor version numbers, like "Mac OSX v10.6.8"---not just "Mac". Also, see this page to quickly check if your OS is supported for the version of Flash Professional you are using.
Tell us about your computer hardware. Include CPU type and number of processor cores, amount of RAM installed, GPU, number of disk drives, and how any external drives are connected.
If you are getting error message(s), what is the full text of the error message(s)?
If you encountered a crash, please upload Flash Professional log files to any free file sharing sites and post a link. Depending on the OS you are using, you will find the crash logs at:
Win: Program Files\Common files\Adobe\Installers or \Documents and Settings\<user>\Local Settings\ApplicationData\Adobe\AAMUpdater\1.0\
Mac: /Library/Logs/Adobe/Installers or ~/ Library/ApplicationSupport/Adobe/AAMUpdater/1.0/
Did you encounter the issue in spite of recreating Flash Professional preferences?
What were you doing when the problem occurred?
Has this ever worked before?
What other software are you running on the system?
Also, do check the Flash Professional FAQs list and also do a quick Flash Professional Community Help search to see if your question has been addressed already.
Adding screenshots and FLAs to your discussions is highly useful and will help fetch an answer faster and easier.I second that. I would also suggest the list of things the user should at least supply is supplemented with the client mode; HI (High Interactivity) or SI (Standard Interactivity).
Axel -
Which method of JSON should I employ when using Flash Professional CS5 to output Air2 AS3 on Windows
I read that Native JSON is not iplemented until Air3 and player 11.
If I am outputing to an Air2 file with AS3 code via Flash Professional CS5 I have been attempting to use the CoreActionscript Libray JSON classes (import com.adobe.serialization.json.JSON).
When testing my code I get errors saying the JSON is not recognised.
Is this method now not supported for my chosen file types.
Can some one advise please.I had saved one copy as an .asp but then resaved it to .xhtml
I'm assuming this is a static web site. Rename (F2) all your pages with .html or .htm extension.
.xhtml is not a valid extension.
Nancy O. -
Why doesnt Adobe just UPDATE Flash Professional? Arent they reinventing the wheel?
Congratulations on getting to open beta with Flash Catalyst!
I know its late in the game to mention something like this but why didnt Abobe just update Flash Professional?
It seems that the arguments for flash Catalyst center around the following:
1) smooth workflow between Photoshop & Illustrator, especially because of the same layer view
2) No coding required to create components out of artwork
3) Can create FXG and FXPs to be used in Flash Builder
4) Can create multi screen aplications
1) 2) and 3) could all be solved by adding a new types of symbols to Flash Professional's 3 currently available symbols(MovieClip, Button, Graphic)
1) could be solved by adding a new Sprite symbol.
Flash Professional needs to be updated to keep up with and match the structure of AS3 anyway.
Sprites were added in AS3 and now wireframe components are being added to the code structure, why not just at that on the design side as well?
Sprites are essentially MovieClips with out a timeline.
So if you created a new Sprite symbol and opened it up in the timeline, you would only see one frame with folders and layers.
A Sprite symbol is essentially organized the in layers and folders and would just like a photoshop file.
And if you really want it to look like a Photoshop layout, then you just move the timeline view over to the right.
This would solve problem 1. Designers could import their artwork into Flash Professional as a Sprite and it would be a seemless experience.
Obviously I'm not saying that a bitmap is a sprite. But I am saying that layers of bitmaps and could be organized inside of a Sprite. And the designer could turn any of the assets into a Button, MovieClip, Graphic, Sprite, and hopefully other Classes and WireframeComponents available in Flash.
2)&3) could be solved by adding a new Symbols for the new Wireframe Components. The Button symbol already has a template with 4 states. Why not update Flash Professional to visually represent more Classes and Component Classes, instead of just the MovieClip Class and the Button Class. Even better, maybe there could be a way to make a template for creating our own wireframe components. Just assign a base class for the wireframe class and a base template, and the introspection view will display accordingly.
States of the component would be listed out at the top instead of frames, just like the Button Symbol used to be. Different layers could be designated for specific graphical parts of the component. The designer would be free to add their own layers if necessary.
In previous versions of Flash, everything was a movieclip and everthing had a timeline. Thats not the case anymore. The timeline is for intropecting MovieClips, but this view could be different when intropsecting different types of symbols such as Sprites, Buttons, Wireframe Components, and even Custom Wireframe Components(extensible).
These new Symbols and also Sprites could export to FXG very easily.
The multi screen applications in 4) look pretty similar to the Slide Presentation Template. Why not just make a new MultiScreen App Template and youre done. these MultiScreenApp Templates could exporte Screens to FXG or export the whole Template to a FXP.
I applaud the work done on the new wireframe components and FXG. Great Job!
But, just cant understand why you cant update Flash Professional with new types of Symbols(Sprites, new Buttons and wireframe Component Classes) and a new MultiScreen App Template.
Flash Professional needs to keep up with AS3 and also needs to export FXG and FXP.
Why doesnt Adobe focus on on this rather than create a new Tool? These features need to be added to Flash Professional anyway.
Isnt there more of a disadvantage to having 2 tools for designers that do the same thing?
I'm sure this issue has been debated before. Can anyone point to me links that have the arguments for creating a separate tool instead of updating?
Has anyone ever suggested that Flash Professional should keep up with AS3?
Has anyone ever suggested making Sprites a new symbol in Flash Professional so that it could be more seamless with Photoshop?
Has anyone ever suggested make Wireframe components in Flash Professional like the Button Symbol in Flash Professional?
Has anyone ever suggested updating Flash Professional so that it would export FXG and FXP?
What is your opinion on this?
-thomasglyn@Ross
Thanks for your explanation. I appreciate your feedback.
I'm glad we agree that ideally there should be 2 main tools, one for designers(Flash Professional) and one for programming(Flash Builder).
You had mentioned "But, that assumes this is possible. As it currently stands it is not" and the reason being "Catalyst, and Builder both use a completely different framework from Professional. The component architecture is drastically different, not to mention the entire backend of the software.".
You could also argue that, the reasons to make a separate flex component creation tool like Flash Catalyst assumes that updating Flash Professional CS4 is NOT possible. But is the statement about the framework being entirely different really true?
Well, that depends on what you mean by the term "framework".
Framework can refer to 3 things in this case.
1) the component framework
2) the code framework(AS3)
3) the flex framework (mxml, fxg)
If you are refering to #1 then you're right, because Adobe hasnt updated the flash component framework in Flash Professional from Flex3 Halo components to Flex4 Spark components.
Flash components have gone through many iterations, and the switch from AS2 to AS3 was probably more profound than the new wireless component structure(Spark). And now that we have AS3, isnt the only difficulty creating a intuitive UI in Flash Professional, and adding export features?
If you are refering to #2 then I think you're incorrect, because Flash Professional has been updated to AS3 and Flex4 Spark components use AS3. I would totally agree with you, if CS4 did not go through all of the trouble updating to AS3.
If you are refering to #3 then you're right, because Flash Professional doesnt export mxml, fxg, or fxp, but with a little creativity, it would probably be possible to allow such an export. Adding FXG/FXP export features could be solved by creating a new type of project file. Adobe did this for AS2, AS3, flash lite, etc. Why cant they just make a new AS3/FXG file that only allows you to build fxg/fxp exportable assets.
Why cant Adobe make a Sprite class the default document class for AS3/FXG projects and when some adds a movie clip asset, export movie clips as swfs or swcs?
So to be honest, after opening up Flash Catalyst again and looking at it again, I almost get the feeling that its just a Flash Component creation tool with a Photoshop UI, for the new AS3/Flex 4 components(Spark components) that Adobe just refuses to add to CS4. CS4 uses AS3 and Spark components use AS3. CS4 needs to be a visual design tool for all the classes in AS3(as much as possible).
Perhaps Adobe originally meant to name this product...
ADOBE FLASH COMPONENTS
Or maybe Adobe Flex Components(but thats no longer true, because Flex 4 will be Flash Builder).
In regard to "reinventing the wheel". Flash components have been reinvented several times, and I totally agree with you that this is important to "reinvent" components to keep up with new techiques as2,as3,fxg. You are right, this is a positive thing. However in this case, I am using "reinvent in a negative sense.
So maybe I shouldnt say "reinvent the wheel", but "reinvent the car".
Perhaps Adobe is trying to create a wheel for the upperclass RIA programmer Flex car, and isnt making it compatible common designer/programmer Flash car. And when they finished the wheel, and they decided just to make a Segway for the Designers and Flash people to ride, that uses this new wheel.
You might argue that its more approachable for designers, and designers feel at home because the ui is similar. This is precisely why Adobe should hurry up and finish updating the ui of the Flash Professional IDE so that its ui is more compatable with Photoshop and Illustrator. The fact that Photoshop and Illustrator is the standard for designers are perhaps one of Adobe's greatest advantages. They could make the designers happy if they just make a Sprite inspector view with layers like photoshop in Flash Professional, instead of using the old "everything
is a movieclip" paridgim. Flash Professional has already upgraded to AS3 and in AS3 everything isnt a movieclip. So it would be nice if they could make views for some of the new classes and wireframe components.
This is the age old debate, update or start from scratch. I guess I'm saying that I think the hard work of updating to AS3 has already been done, and its just plain wierd that Adobe decides to build a separte tool for components, when they use the same AS3 code base.
Its just insanely exciting to just think about what could have been if Flash updated and brought on more Designers and at the same time linked in the Flex community. Thats what Flash has always been about! The meeting point between Designers and Programmers.
To go this far and quit just because of components just leaves me blue.
It seems that many projects stop at 80% complete and if the developers just spent the extra 20% on fine tuning things then they would have a very high quality product. In this case the remaining 20% is components, ui, and export. I understand that there are probably many things I dont understand, especially when you through in marketing, and product life cycle.
But I think Adobe could have done it, if they put as much effort into it as they did to make an entirely new product.
Maybe we should make some noise before its too late.
I'm still interested in seeing more links that show the logic behind the initial discussions of this debate when it was first decided.
pls keep me posted.
@nwfa & macsavers
Yes, youre right. it does seem to be their plan. I just hope they are just testing the waters. Perhaps after they do the initial selling of Flash Compenents, then maybe they could offer a free update to CS4.
As I mentioned above, the main reason designers feel at home is because of the UI of Flash Catalyst. UI's can be updated, and I believe Flash Professional can and should update itsui for the reasons I mentioned above. -
Trying to understand capabilities of Flash Professional and Flash Builder 4
I recently purchased the CS5 Master Collection and am struggling to understand the uses for Flash Professional and Flash Builder 4. I was inspired by Jay Pavlina's Super Mario Crossover game and wish to make similar applications.
However, I am confused about whether I should be using Flash Professional or Flash Builder 4 or both? I purchased the two books that Jay Pavlina recommended "ActionScript 3.0 Animation Making Things Move!" and "Essential ActionScript 3.0". I've been trying to find resources that will help me understand exactly the purpose of each of these applications.
It appears to me that ActionScript 3.0 is used in both? So which one should I be using? Or both? Or is one more design oriented and the other more development oriented? Can one make flash game like Jay's using just one or the other? Any help would be greatly appreciated.I thought about it a bit more. I think you should take my advice with a grain of salt. I am still standing behind what I said but there are some circumstances that we are not in control of.
If your task is to be the beginning and the end of your code - don't bother with Flash IDE. BUT, if you plan to monetize on your Flash/ActionScript skills, you may not have choice but be familiar with as many environments as possible.
Here is my personal experiense that illustrates this point.
I always prayed to gods, chanted to mandalas and made offerings to spirits to avoid a single thing - not ever deal with custom Flash components. Rightly or wrongly I perceive them as one of the lamest Macromedia creations. I am not talking about SWCs but about this thing that you create with preview and all other crap. Above all, it did not (and still doesn't) make much sense to me from functionality standpoint.
Anyway, as, I guess, a karmic retribution, I was dealt this card. I got involved in a project(s) where I was not told that my main task would be to, you are right, write and reverse engineer Flash custom components. If I did not know Flash IDE I would be totally lost. Custom components are so counter-intuitive that only people without programming background can view them as a convenience. Well, it is a convenience if they are written correctly.
The point is that, if you want to make a career out of it, you should gradually get involved with Flash IDE for now. The truth is that there are tons of agencies out there that do not have resources to hire high level developers and they employ "drag n' drop, cut n' paste" individuals. And this is a real market segment. Even well seasoned development houses have to succumb to this reality and cater to such entities.
It is your choice, of course, but I thought it wouldn't be fare to you to be very fascist about pushing my one-sided views. -
Document or video tutorial for setting LiveCycle Collaboration Service in Flash Professional CS5
Hello,
I want to use Adobe LiveCycle Collaboration Service for my company, but the problem is, I work upon Flash Professional and i dont have grip towards Flex, the documentation that is provided with sdk is of Flex,
so, I want 2 types of help,
1) If i want to setup LiveCycle Collaboration Service , will i get the document for that,
If it is not available please provide me help for customizing skin of toolbar in SharedWhiteboard of LCCS,
Thanks,
Rajiv(another potential double-post, don't know why my emails to the forum are being ignored...)
Hi Rajiv
For Flash-only projects, check out the 3 sample applications which start
with "Flash" - FlashUserList, FlashWebCamExample, and FlashSimpleChat. These
should get you up and running with CS5.
Unfortunately, if you're not using Flex, you'll find that the
SharedWhiteBoard isn't going to work - it's completely Flex based. You could
use the SharedWhiteBoardModel and write your own, but unfortunately
whiteboards are pretty complicated and require quite a bit of work (this is
why we didn't port it from Flex to Flash - no one has asked for it until
now, and it's a ton of work).
hope that helps
nigel -
Who can explain what I need to do when actionScript doesn't seem to work in my trial cc version of flash professional, sometimes I use cs5.5 related AS3?
thanks for a reply,
mikedid you get my earlier message? Here's what I wrote;
I also meant to add the way the instructor for the course showed how to
write the code
for example; home_btn.addEventListener(Mouse...................) as so
on You mention no period after the btn unless a width or something how
could I change the code to be proper.
and also one for {
content_pg.gotoAndStop(2);
same period example. should there be a space and no period after home_btn?
thanks again for your assistance.
mike
On Wed, Aug 27, 2014 at 7:00 PM, -mikey1969- <[email protected]> -
What is Flash Professional CS6? | Learn Flash Professional CS6 | Adobe TV
Dive into Adobe Flash Professional CS6. See how web designers, developers, and animators can use Flash to create rich content for screen and web environments.
http://adobe.ly/Jo2HUOActually, what Flash Pro is, is a profound disappointment. I've been using Flash since Macromedia days and have generally put up with the huge change in focus that's happened between AS2 and AS3. I was irked by the sudden need to have to declare classes for even the simplest functions but lived with it because there was nothing much else out there. It wasn't until very recently that the truth finally dawned on me; Flash is a bloody mess.
Adobe have completely betrayed the design community and after long consideration I've come to the conclusion that Apple were entirely right to prevent Flash appearing on iOS devices. I don't want to have to write reams of code to make a simple ad, it's a waste of time and money and my clients really don't care whether their code is elegant or not. All that matters is pixels on screen.
Flash has completely lost its way. Instead of being a ground-breaking design tool it's just another OOPL with a half-baked IDE. What's the point of Flash? It's a product which is now conceptually flawed, a scripting language with a few graphic bolt-ons, a tool which actually reduces productivity instead of enhancing it.
The name Flash Pro is misleading, it should be called ActionScript Pro. Flash has become a programming tool only, and in the process thrown up so many barriers to productivity that it's become all but unusable in the purpose for which it was originally conceived.
It seems to me that Adobe lack the imagination to produce ground-breaking products any more. All they deliver are engineering solutions with incremental improvements and that's only a good enough solution whilst there's nothing else out there. Quite evidently the ground is shifting and as a product Flash is clinging on to the edge of a cliff. Flash is exposed.
In the 21st century it seems extraordinary that a product marketing itself as a design tool requires designers to start a creative project by deciding which packages to import. This is useful to me why? Does my client give a damn? Why doesn't the application work that out for itself? It's like asking a driver to service their own engine every time they take the car out. Sure, a knowledge of code is beneficial but starting from first principles every time you start a project? It's just not good enough.
I'll keep using Flash for now, but as soon as something new gains sufficient critical mass - Corona, Kwik 2, anything that actually gives designers productivity tools - I'm out of here. -
Spark Skinning and Flash Professional
Hello,
In transitioning to Flex Builder fom Flex 3, I am running into a wall with the whole spark component architecture. I used to create my visual content in Flash, convert those assets to symbols and then reference the skin classes using an external CSS file. This may not have been the most elegant way to do things, but it allowed me to leverage my proficiency in Flash (and tons of existing assets) to create a workflow that was as flexible as I needed it to be, while at the same time allowing me to make changes easily and rapidly.
I am a single designer/developer, so this 'separation' of everything between 'designers' and 'developers' is creating some serious drag on my workflow. I just don't understand how this new spark workflow model can possibly be viewed as 'efficient' when it adds so much overhead and boilerplate code to my projects. I used to go from vector graphics (using 9 slice scaling) directly into my Flex projects, and now I have to filter all of these vectors through catalyst, and then create these skin classes which require the tweaking of the catalyst output for me to use them (which, in effect, destroys the round-trip editing of the catalyst projects).
I must be missing something major because, it just doesn't make any sense to me. I know that I can always use the mx components to continue to work the way I am now, but to what end ? I get these warnings that all but tell me the mx buttons are going to be deprecated sooner or later so what should I do ? Just because it's possible to represent vectors with xml doesn't mean that it's a good idea. It seems as if Adobe took something that was optimized (at least for my workflow), and turned it upside down and made things so much more labor-intensive, with no real benefits. I'd use CSS until I couldn't achieve the appearance I wanted, and then for the rest I'd skin the components in Flash Professional.
If you are still reading this, thank you. I really only have a couple of simple questions: Are MX components going to be deprecated ?, which, I know only Adobe folk can answer, and the more important question (for me): Does a workflow exist between Flash Professional and Flash Builder for the skinning of spark components. I have read a couple of other posts which ask similar questions, and some have 'solutions', but again, these seem to be ways to work around the new component architecture, rather than how to maximize it's efficiency and effectiveness.
I feel like I should have just stayed with Flex Builder, and Flash Pro because the newest version of Flash Builder just seems more and more like a tweener version that I could have skipped altogether and waited for the platform to mature a little more.
Thanks for staying with me, I apologize for the rambling.I can't really help you pick the best MVC framework, but I can recommend that if you are moving your Flex 3 projects to Flex 4, make as few changes as possible for moving components right now. Like you said, we are in the middle of a transition. The Adobe guys recommend not porting all of your mx Projects over to Spark. I have a large Flex 3 project that I'm almost finished moving to 4.1 and I have changed as little as possible. The only reason I converted it was to take advantage of some of the nice things they've done with data services and binding.
I don't think it is a waste of time to take Flex 3 projects and make them run in Flex 4.1 or higher, but I do think it is a waste of time to convert all of those components over to their Spark counterparts at this time. -
(How can we) Import Flash Professional .FLA file format?
How can we import a Flash Professional .fla file format into Flash Catalyst? It would appear that we can't...at least not yet! I have added this as a feature request within the adobe labs site for Catalyst. Someone at Adobe suggested that I also explore the forums, so here we are. If you would also like to have this feature added, please let Adobe know by promoting the
idea.
Our use case is this: we have a large Flash file with a library of over one thousand skins and assets that were built in Flash with Adobe's Flex Skins Templates. These stateful, graphical skins were used within a custom theme by several Flex 3 projects.
Now that we are looking to migrate to FlashBuilder 4, and start to use Spark components, we are trying to find a workflow that allows us to use Adobe tools and to reuse our existing vector artwork. Since we have such a large number of assets, we are exploring various approaches, including the use of JSFL. So far we haven't found a good way to migrate from Flash-built skins for Flex 3 to Catalyst-built skins for FlashBuilder 4.Hi Ajay,
See attached V 7.0 example...
Hope it helps,
Nick
Attachments:
Read_txt_File.vi 20 KB -
(How can we) Export FXG from Flash Professional using JSFL
How can we export a selection from Flash Professional as .FXG using JSFL? It appears that this is not possible... just yet! I have added this as a feature request within the Adobe Labs site for Flash Professional. Someone at Adobe suggested that I also explore the forums, so here we are. If you would also like to have this feature added, please let Adobe know by promoting the idea.
Our use case is this: we have a large Flash file with a library of over one thousand skins and assets that were built in Flash with Adobe's Flex Skins Templates. These stateful, graphical skins were used within a custom theme by several Flex 3 projects. Our ultimate goal is to bring these through Catalyst, maintaining their vectors, and use them to create Spark skins.
We've got a JSFL that can export each linked library asset, as well as any frame-labeled 'state' within these clips. However, currently we are using exportPNG, which is not ideal as it flattens our vector art into raster images. We are about to try the exportSWF option, and see what Flash Catalyst does with this. Our early attemps with importing swf's haven't been too amazing.
I'm starting to imagine some cross-product scripting in which we export symbols at a state-by-state level as .swf from Flash, then rebuild these onto layers in Illustrator, and THEN import these into Catalyst...yikes!
Anyone have a better solution?Follow-up:
Out of pure wishful thinking I decided I would just see what happened if I pretended 'exportFXG' was already a part of JSFL. Based on the signature of 'exportPNG', i tried the following lines:
var success = fl.getDocumentDOM().exportFXG("file:///C:/mySymbol.fxg");
fl.trace("success:"+success); // output: success:true
It worked! Fantastic! I'm not sure if exportFXG is considered still in "beta" and therefore intentionally excluded from the docs, or if it was just an oversight. But at least it gives us something to experiment with. -
In Flash Professional CS6 I made a motion tween. As I scroll along the timeline I right click to Free Transform the object so it hits specif locations as the timeline goes along. After a few points have been adjusted, the program crashes without warning.
I am using a Macbook Pro, bought in 2011 (just reached two years old). I have the Mountain Lion operating system. The version of flash that I have is 12.0.2.529 and I have completed all the updates which are online. Scroll down to see System Info and the Crash Report.
In the image below you can see the timeline. All the little dots are points that have been altered in the motion tween. On the stage you can see part of a bounding box. This is when the transform tool is on. As soon as I move the point while holding option, the program crashes.
Has anyone had issues of Flash Pro crashing for no reason? Found this link online: http://helpx.adobe.com/flash/kb/mountain-lion-support-flash-professional.html. Should I instal Flash CS5 instead?
System Info:
Processor: 2 GHz Intel Core i7
Number of Cores: 4
Memory: 4 GB 1333 MHz DDR3
Graphics: Intel HD Graphics 3000 384 MB
Software: OS X 10.8.4
CRASH REPORT:
Process: Adobe Flash CS6 [1041]
Path: /Applications/Utilities/Adobe Master Collection/*/Adobe Flash CS6.app/Contents/MacOS/Adobe Flash CS6
Identifier: com.adobe.flash
Version: 12.0.2.529 (12.0.2)
Code Type: X86 (Native)
Parent Process: launchd [137]
User ID: 501
Date/Time: 2013-07-02 16:58:34.175 -0400
OS Version: Mac OS X 10.8.4 (12E55)
Report Version: 10
Interval Since Last Report: 66369 sec
Crashes Since Last Report: 13
Per-App Interval Since Last Report: 1528 sec
Per-App Crashes Since Last Report: 1
Anonymous UUID: 9B3BCE74-CBC9-FC6D-1860-4C792E606054
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Application Specific Information:
terminate called without an active exception
abort() called
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x97b6ba6a __pthread_kill + 10
1 libsystem_c.dylib 0x936c0b2f pthread_kill + 101
2 libsystem_c.dylib 0x936f74ec abort + 168
3 libc++abi.dylib 0x9800d7e0 abort_message + 151
4 libc++abi.dylib 0x9800b257 default_terminate() + 48
5 libc++abi.dylib 0x9800b289 safe_handler_caller(void (*)()) + 13
6 libc++abi.dylib 0x9800b2f1 std::terminate() + 23
7 libc++abi.dylib 0x9800c472 __cxa_rethrow + 83
8 com.adobe.flash 0x012c5861 std::vector<int, std::allocator<int> >::_M_fill_insert(__gnu_cxx::__normal_iterator<int*, std::vector<int, std::allocator<int> > >, unsigned long, int const&) + 24899
9 com.adobe.flash 0x00e2bbde std::vector<int, std::allocator<int> >::insert(__gnu_cxx::__normal_iterator<int*, std::vector<int, std::allocator<int> > >, int const&) + 73930
10 com.adobe.flash 0x003c473c std::vector<std::pair<CString, CString>, std::allocator<std::pair<CString, CString> > >::push_back(std::pair<CString, CString> const&) + 33564
11 com.adobe.flash 0x00465bea CreateRegion::~CreateRegion() + 18172
12 com.adobe.flash 0x003b3d7c CDrawMac::~CDrawMac() + 180002
13 com.adobe.flash 0x00fe727f CRgn::~CRgn() + 3869
14 com.adobe.flash 0x00f9d7e9 CDocManager::GetNextDocTemplate(__POSITION*&) const + 12251
15 com.adobe.flash 0x00fa1fde CControlBar::GetRuntimeClass() const + 3504
16 com.adobe.flash 0x01064838 cf_bad_change::~cf_bad_change() + 3550
17 com.apple.HIToolbox 0x9038f9bb _InvokeEventHandlerUPP(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*, long (*)(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*)) + 36
18 com.apple.HIToolbox 0x90217394 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1343
19 com.apple.HIToolbox 0x90216780 SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 430
20 com.apple.HIToolbox 0x9022a655 SendEventToEventTarget + 88
21 com.apple.HIToolbox 0x9039a922 SendEventFromMouseDown(OpaqueWindowPtr*, unsigned long, OpaqueEventRef*) + 167
22 com.apple.HIToolbox 0x9039acc4 HandleWindowClick(OpaqueWindowPtr*, Point, short, unsigned long, OpaqueEventRef*) + 540
23 com.apple.HIToolbox 0x9039a2f3 HandleMouseEvent(OpaqueEventHandlerCallRef*, OpaqueEventRef*) + 826
24 com.apple.HIToolbox 0x90202838 StandardWindowEventHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 85
25 com.apple.HIToolbox 0x9038f9bb _InvokeEventHandlerUPP(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*, long (*)(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*)) + 36
26 com.apple.HIToolbox 0x90217394 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1343
27 com.apple.HIToolbox 0x90216780 SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 430
28 com.apple.HIToolbox 0x90201dda CallNextEventHandler + 84
29 com.adobe.flash 0x00fa32e0 CControlBar::GetRuntimeClass() const + 8370
30 com.adobe.flash 0x01064838 cf_bad_change::~cf_bad_change() + 3550
31 com.apple.HIToolbox 0x9038f9bb _InvokeEventHandlerUPP(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*, long (*)(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*)) + 36
32 com.apple.HIToolbox 0x90217394 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1343
33 com.apple.HIToolbox 0x90216780 SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 430
34 com.apple.HIToolbox 0x9022a655 SendEventToEventTarget + 88
35 com.apple.HIToolbox 0x9024a5c7 ToolboxEventDispatcherHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 2141
36 com.apple.HIToolbox 0x9021783f DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 2538
37 com.apple.HIToolbox 0x90216780 SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 430
38 com.apple.HIToolbox 0x9022a655 SendEventToEventTarget + 88
39 com.apple.HIToolbox 0x9038f0b7 ToolboxEventDispatcher + 82
40 com.apple.HIToolbox 0x9038ef79 RunApplicationEventLoop + 240
41 com.adobe.flash 0x00fcd77b CArray<MACFTYPES*, MACFTYPES*>::SetSize(int, int) + 5271
42 com.adobe.flash 0x00fa619d CTimerImpl::~CTimerImpl() + 1293
43 com.adobe.flash 0x00fa6380 CTimerImpl::~CTimerImpl() + 1776
44 com.adobe.flash 0x0020f46d std::vector<Symmetry*, std::allocator<Symmetry*> >::vector(std::allocator<Symmetry*> const&) + 6295
Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0 libsystem_kernel.dylib 0x97b6c9ae kevent + 10
1 libdispatch.dylib 0x9a644c71 _dispatch_mgr_invoke + 993
2 libdispatch.dylib 0x9a6447a9 _dispatch_mgr_thread + 53
Thread 2:
0 libsystem_kernel.dylib 0x97b6b8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x936c4280 _pthread_cond_wait + 833
2 libsystem_c.dylib 0x9374a095 pthread_cond_wait$UNIX2003 + 71
3 com.apple.CoreServices.CarbonCore 0x96227492 TSWaitOnCondition + 128
4 com.apple.CoreServices.CarbonCore 0x9622768e TSWaitOnConditionTimedRelative + 146
5 com.apple.CoreServices.CarbonCore 0x96173acb MPWaitOnQueue + 261
6 com.adobe.ACE 0x06b81a69 0x6b42000 + 260713
7 com.adobe.ACE 0x06b80d99 0x6b42000 + 257433
8 com.apple.CoreServices.CarbonCore 0x961faa7b PrivateMPEntryPoint + 68
9 libsystem_c.dylib 0x936bf5b7 _pthread_start + 344
10 libsystem_c.dylib 0x936a9d4e thread_start + 34
Thread 3:
0 libsystem_kernel.dylib 0x97b6b8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x936c4280 _pthread_cond_wait + 833
2 libsystem_c.dylib 0x9374a095 pthread_cond_wait$UNIX2003 + 71
3 com.apple.CoreServices.CarbonCore 0x96227492 TSWaitOnCondition + 128
4 com.apple.CoreServices.CarbonCore 0x9622768e TSWaitOnConditionTimedRelative + 146
5 com.apple.CoreServices.CarbonCore 0x96173acb MPWaitOnQueue + 261
6 com.adobe.ACE 0x06b81a69 0x6b42000 + 260713
7 com.adobe.ACE 0x06b80d99 0x6b42000 + 257433
8 com.apple.CoreServices.CarbonCore 0x961faa7b PrivateMPEntryPoint + 68
9 libsystem_c.dylib 0x936bf5b7 _pthread_start + 344
10 libsystem_c.dylib 0x936a9d4e thread_start + 34
Thread 4:
0 libsystem_kernel.dylib 0x97b6b8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x936c4280 _pthread_cond_wait + 833
2 libsystem_c.dylib 0x9374a095 pthread_cond_wait$UNIX2003 + 71
3 com.apple.CoreServices.CarbonCore 0x96227492 TSWaitOnCondition + 128
4 com.apple.CoreServices.CarbonCore 0x9622768e TSWaitOnConditionTimedRelative + 146
5 com.apple.CoreServices.CarbonCore 0x96173acb MPWaitOnQueue + 261
6 com.adobe.ACE 0x06b81a69 0x6b42000 + 260713
7 com.adobe.ACE 0x06b80d99 0x6b42000 + 257433
8 com.apple.CoreServices.CarbonCore 0x961faa7b PrivateMPEntryPoint + 68
9 libsystem_c.dylib 0x936bf5b7 _pthread_start + 344
10 libsystem_c.dylib 0x936a9d4e thread_start + 34
Thread 5:
0 libsystem_kernel.dylib 0x97b6b8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x936c4280 _pthread_cond_wait + 833
2 libsystem_c.dylib 0x9374a095 pthread_cond_wait$UNIX2003 + 71
3 com.apple.CoreServices.CarbonCore 0x96227492 TSWaitOnCondition + 128
4 com.apple.CoreServices.CarbonCore 0x9622768e TSWaitOnConditionTimedRelative + 146
5 com.apple.CoreServices.CarbonCore 0x96173acb MPWaitOnQueue + 261
6 com.adobe.ACE 0x06b81a69 0x6b42000 + 260713
7 com.adobe.ACE 0x06b80d99 0x6b42000 + 257433
8 com.apple.CoreServices.CarbonCore 0x961faa7b PrivateMPEntryPoint + 68
9 libsystem_c.dylib 0x936bf5b7 _pthread_start + 344
10 libsystem_c.dylib 0x936a9d4e thread_start + 34
Thread 6:
0 libsystem_kernel.dylib 0x97b6b8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x936c4280 _pthread_cond_wait + 833
2 libsystem_c.dylib 0x9374a095 pthread_cond_wait$UNIX2003 + 71
3 com.apple.CoreServices.CarbonCore 0x96227492 TSWaitOnCondition + 128
4 com.apple.CoreServices.CarbonCore 0x9622768e TSWaitOnConditionTimedRelative + 146
5 com.apple.CoreServices.CarbonCore 0x96173acb MPWaitOnQueue + 261
6 com.adobe.ACE 0x06b81a69 0x6b42000 + 260713
7 com.adobe.ACE 0x06b80d99 0x6b42000 + 257433
8 com.apple.CoreServices.CarbonCore 0x961faa7b PrivateMPEntryPoint + 68
9 libsystem_c.dylib 0x936bf5b7 _pthread_start + 344
10 libsystem_c.dylib 0x936a9d4e thread_start + 34
Thread 7:
0 libsystem_kernel.dylib 0x97b6b8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x936c4280 _pthread_cond_wait + 833
2 libsystem_c.dylib 0x9374a095 pthread_cond_wait$UNIX2003 + 71
3 com.apple.CoreServices.CarbonCore 0x96227492 TSWaitOnCondition + 128
4 com.apple.CoreServices.CarbonCore 0x9622768e TSWaitOnConditionTimedRelative + 146
5 com.apple.CoreServices.CarbonCore 0x96173acb MPWaitOnQueue + 261
6 com.adobe.ACE 0x06b81a69 0x6b42000 + 260713
7 com.adobe.ACE 0x06b80d99 0x6b42000 + 257433
8 com.apple.CoreServices.CarbonCore 0x961faa7b PrivateMPEntryPoint + 68
9 libsystem_c.dylib 0x936bf5b7 _pthread_start + 344
10 libsystem_c.dylib 0x936a9d4e thread_start + 34
Thread 8:
0 libsystem_kernel.dylib 0x97b6b8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x936c4280 _pthread_cond_wait + 833
2 libsystem_c.dylib 0x9374a095 pthread_cond_wait$UNIX2003 + 71
3 com.apple.CoreServices.CarbonCore 0x96227492 TSWaitOnCondition + 128
4 com.apple.CoreServices.CarbonCore 0x9622768e TSWaitOnConditionTimedRelative + 146
5 com.apple.CoreServices.CarbonCore 0x96173acb MPWaitOnQueue + 261
6 com.adobe.ACE 0x06b81a69 0x6b42000 + 260713
7 com.adobe.ACE 0x06b80d99 0x6b42000 + 257433
8 com.apple.CoreServices.CarbonCore 0x961faa7b PrivateMPEntryPoint + 68
9 libsystem_c.dylib 0x936bf5b7 _pthread_start + 344
10 libsystem_c.dylib 0x936a9d4e thread_start + 34
Thread 9:
0 libsystem_kernel.dylib 0x97b6b8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x936c4280 _pthread_cond_wait + 833
2 libsystem_c.dylib 0x9374a095 pthread_cond_wait$UNIX2003 + 71
3 com.adobe.AFlame 0x0bd61439 Flame_Terminate + 1281926
4 com.adobe.AFlame 0x0bdab950 Flame_Terminate + 1586333
5 com.adobe.AFlame 0x0bd5fa35 Flame_Terminate + 1275266
6 libsystem_c.dylib 0x936bf5b7 _pthread_start + 344
7 libsystem_c.dylib 0x936a9d4e thread_start + 34
Thread 10:
0 libsystem_kernel.dylib 0x97b6bb3e __recvfrom + 10
1 libsystem_c.dylib 0x93749bbf recv$UNIX2003 + 54
2 ServiceManager-Launcher.dylib 0x17f69733 Invoke + 47867
3 ServiceManager-Launcher.dylib 0x17f68846 Invoke + 44046
4 ServiceManager-Launcher.dylib 0x17f67988 Invoke + 40272
5 ServiceManager-Launcher.dylib 0x17f67a0f Invoke + 40407
6 ServiceManager-Launcher.dylib 0x17f62baf Invoke + 20343
7 ServiceManager-Launcher.dylib 0x17f62ea7 Invoke + 21103
8 ServiceManager-Launcher.dylib 0x17f63685 Invoke + 23117
9 ServiceManager-Launcher.dylib 0x17f638f9 Invoke + 23745
10 ServiceManager-Launcher.dylib 0x17f662a0 Invoke + 34408
11 ServiceManager-Launcher.dylib 0x17f663fd Invoke + 34757
12 ServiceManager-Launcher.dylib 0x17f66c91 Invoke + 36953
13 ServiceManager-Launcher.dylib 0x17f66db2 Invoke + 37242
14 ServiceManager-Launcher.dylib 0x17f59656 Login + 461
15 ServiceManager-Launcher.dylib 0x17f5d09a Login + 15377
16 ServiceManager-Launcher.dylib 0x17f67165 Invoke + 38189
17 ServiceManager-Launcher.dylib 0x17f692eb Invoke + 46771
18 libsystem_c.dylib 0x936bf5b7 _pthread_start + 344
19 libsystem_c.dylib 0x936a9d4e thread_start + 34
Thread 11:: Java: Exception Handler Thread
0 libsystem_kernel.dylib 0x97b697d2 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x97b68cb0 mach_msg + 68
2 libsystem_kernel.dylib 0x97b69644 mach_msg_server + 620
3 libjvm.dylib 0x26c25a5a 0x26c10000 + 88666
4 libjvm.dylib 0x26c258e3 0x26c10000 + 88291
5 libjvm.dylib 0x26c2436c 0x26c10000 + 82796
6 libsystem_c.dylib 0x936bf5b7 _pthread_start + 344
7 libsystem_c.dylib 0x936a9d4e thread_start + 34
Thread 12:: Java: Gang worker#0 (Parallel GC Threads)
0 libsystem_kernel.dylib 0x97b697d2 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x97b68cb0 mach_msg + 68
2 libjvm.dylib 0x26c24ac6 0x26c10000 + 84678
3 libjvm.dylib 0x26c24a02 0x26c10000 + 84482
4 libjvm.dylib 0x26c248c8 0x26c10000 + 84168
5 libjvm.dylib 0x26c2440d 0x26c10000 + 82957
6 libjvm.dylib 0x26c24297 0x26c10000 + 82583
7 libjvm.dylib 0x26c3bdad 0x26c10000 + 179629
8 libjvm.dylib 0x26c3bc97 0x26c10000 + 179351
9 libjvm.dylib 0x26c2436c 0x26c10000 + 82796
10 libsystem_c.dylib 0x936bf5b7 _pthread_start + 344
11 libsystem_c.dylib 0x936a9d4e thread_start + 34
Thread 13:: Java: Gang worker#1 (Parallel GC Threads)
0 libsystem_kernel.dylib 0x97b697d2 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x97b68cb0 mach_msg + 68
2 libjvm.dylib 0x26c24ac6 0x26c10000 + 84678
3 libjvm.dylib 0x26c24a02 0x26c10000 + 84482
4 libjvm.dylib 0x26c248c8 0x26c10000 + 84168
5 libjvm.dylib 0x26c2440d 0x26c10000 + 82957
6 libjvm.dylib 0x26c24297 0x26c10000 + 82583
7 libjvm.dylib 0x26c3bdad 0x26c10000 + 179629
8 libjvm.dylib 0x26c3bc97 0x26c10000 + 179351
9 libjvm.dylib 0x26c2436c 0x26c10000 + 82796
10 libsystem_c.dylib 0x936bf5b7 _pthread_start + 344
11 libsystem_c.dylib 0x936a9d4e thread_start + 34
Thread 14:: Java: Gang worker#2 (Parallel GC Threads)
0 libsystem_kernel.dylib 0x97b697d2 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x97b68cb0 mach_msg + 68
2 libjvm.dylib 0x26c24ac6 0x26c10000 + 84678
3 libjvm.dylib 0x26c24a02 0x26c10000 + 84482
4 libjvm.dylib 0x26c248c8 0x26c10000 + 84168
5 libjvm.dylib 0x26c2440d 0x26c10000 + 82957
6 libjvm.dylib 0x26c24297 0x26c10000 + 82583
7 libjvm.dylib 0x26c3bdad 0x26c10000 + 179629
8 libjvm.dylib 0x26c3bc97 0x26c10000 + 179351
9 libjvm.dylib 0x26c2436c 0x26c10000 + 82796
10 libsystem_c.dylib 0x936bf5b7 _pthread_start + 344
11 libsystem_c.dylib 0x936a9d4e thread_start + 34
Thread 15:: Java: Gang worker#3 (Parallel GC Threads)
0 libsystem_kernel.dylib 0x97b697d2 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x97b68cb0 mach_msg + 68
2 libjvm.dylib 0x26c24ac6 0x26c10000 + 84678
3 libjvm.dylib 0x26c24a02 0x26c10000 + 84482
4 libjvm.dylib 0x26c248c8 0x26c10000 + 84168
5 libjvm.dylib 0x26c2440d 0x26c10000 + 82957
6 libjvm.dylib 0x26c24297 0x26c10000 + 82583
7 libjvm.dylib 0x26c3bdad 0x26c10000 + 179629
8 libjvm.dylib 0x26c3bc97 0x26c10000 + 179351
9 libjvm.dylib 0x26c2436c 0x26c10000 + 82796
10 libsystem_c.dylib 0x936bf5b7 _pthread_start + 344
11 libsystem_c.dylib 0x936a9d4e thread_start + 34
Thread 16:: Java: Gang worker#4 (Parallel GC Threads)
0 libsystem_kernel.dylib 0x97b697d2 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x97b68cb0 mach_msg + 68
2 libjvm.dylib 0x26c24ac6 0x26c10000 + 84678
3 libjvm.dylib 0x26c24a02 0x26c10000 + 84482
4 libjvm.dylib 0x26c248c8 0x26c10000 + 84168
5 libjvm.dylib 0x26c2440d 0x26c10000 + 82957
6 libjvm.dylib 0x26c24297 0x26c10000 + 82583
7 libjvm.dylib 0x26c3bdad 0x26c10000 + 179629
8 libjvm.dylib 0x26c3bc97 0x26c10000 + 179351
9 libjvm.dylib 0x26c2436c 0x26c10000 + 82796
10 libsystem_c.dylib 0x936bf5b7 _pthread_start + 344
11 libsystem_c.dylib 0x936a9d4e thread_start + 34
Thread 17:: Java: Gang worker#5 (Parallel GC Threads)
0 libsystem_kernel.dylib 0x97b697d2 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x97b68cb0 mach_msg + 68
2 libjvm.dylib 0x26c24ac6 0x26c10000 + 84678
3 libjvm.dylib 0x26c24a02 0x26c10000 + 84482
4 libjvm.dylib 0x26c248c8 0x26c10000 + 84168
5 libjvm.dylib 0x26c2440d 0x26c10000 + 82957
6 libjvm.dylib 0x26c24297 0x26c10000 + 82583
7 libjvm.dylib 0x26c3bdad 0x26c10000 + 179629
8 libjvm.dylib 0x26c3bc97 0x26c10000 + 179351
9 libjvm.dylib 0x26c2436c 0x26c10000 + 82796
10 libsystem_c.dylib 0x936bf5b7 _pthread_start + 344
11 libsystem_c.dylib 0x936a9d4e thread_start + 34
Thread 18:: Java: Gang worker#6 (Parallel GC Threads)
0 libsystem_kernel.dylib 0x97b697d2 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x97b68cb0 mach_msg + 68
2 libjvm.dylib 0x26c24ac6 0x26c10000 + 84678
3 libjvm.dylib 0x26c24a02 0x26c10000 + 84482
4 libjvm.dylib 0x26c248c8 0x26c10000 + 84168
5 libjvm.dylib 0x26c2440d 0x26c10000 + 82957
6 libjvm.dylib 0x26c24297 0x26c10000 + 82583
7 libjvm.dylib 0x26c3bdad 0x26c10000 + 179629
8 libjvm.dylib 0x26c3bc97 0x26c10000 + 179351
9 libjvm.dylib 0x26c2436c 0x26c10000 + 82796
10 libsystem_c.dylib 0x936bf5b7 _pthread_start + 344
11 libsystem_c.dylib 0x936a9d4e thread_start + 34
Thread 19:: Java: Gang worker#7 (Parallel GC Threads)
0 libsystem_kernel.dylib 0x97b697d2 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x97b68cb0 mach_msg + 68
2 libjvm.dylib 0x26c24ac6 0x26c10000 + 84678
3 libjvm.dylib 0x26c24a02 0x26c10000 + 84482
4 libjvm.dylib 0x26c248c8 0x26c10000 + 84168
5 libjvm.dylib 0x26c2440d 0x26c10000 + 82957
6 libjvm.dylib 0x26c24297 0x26c10000 + 82583
7 libjvm.dylib 0x26c3bdad 0x26c10000 + 179629
8 libjvm.dylib 0x26c3bc97 0x26c10000 + 179351
9 libjvm.dylib 0x26c2436c 0x26c10000 + 82796
10 libsystem_c.dylib 0x936bf5b7 _pthread_start + 344
11 libsystem_c.dylib 0x936a9d4e thread_start + 34
Thread 20:: Java: Gang worker#0 (Parallel CMS Threads)
0 libsystem_kernel.dylib 0x97b697d2 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x97b68cb0 mach_msg + 68
2 libjvm.dylib 0x26c24ac6 0x26c10000 + 84678
3 libjvm.dylib 0x26c24a02 0x26c10000 + 84482
4 libjvm.dylib 0x26c248c8 0x26c10000 + 84168
5 libjvm.dylib 0x26c2440d 0x26c10000 + 82957
6 libjvm.dylib 0x26c24297 0x26c10000 + 82583
7 libjvm.dylib 0x26f21e72 0x26c10000 + 3219058
8 libjvm.dylib 0x26c3bc97 0x26c10000 + 179351
9 libjvm.dylib 0x26c2436c 0x26c10000 + 82796
10 libsystem_c.dylib 0x936bf5b7 _pthread_start + 344
11 libsystem_c.dylib 0x936a9d4e thread_start + 34
Thread 21:: Java: Gang worker#1 (Parallel CMS Threads)
0 libsystem_kernel.dylib 0x97b697d2 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x97b68cb0 mach_msg + 68
2 libjvm.dylib 0x26c24ac6 0x26c10000 + 84678
3 libjvm.dylib 0x26c24a02 0x26c10000 + 84482
4 libjvm.dylib 0x26c248c8 0x26c10000 + 84168
5 libjvm.dylib 0x26c2440d 0x26c10000 + 82957
6 libjvm.dylib 0x26c24297 0x26c10000 + 82583
7 libjvm.dylib 0x26f21e72 0x26c10000 + 3219058
8 libjvm.dylib 0x26c3bc97 0x26c10000 + 179351
9 libjvm.dylib 0x26c2436c 0x26c10000 + 82796
10 libsystem_c.dylib 0x936bf5b7 _pthread_start + 344
11 libsystem_c.dylib 0x936a9d4e thread_start + 34
Thread 22:: Java: Concurrent Mark-Sweep GC Thread
0 libsystem_kernel.dylib 0x97b697d2 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x97b68cb0 mach_msg + 68
2 libjvm.dylib 0x26c24b96 0x26c10000 + 84886
3 libjvm.dylib 0x26c4271a 0x26c10000 + 206618
4 libjvm.dylib 0x26c248e4 0x26c10000 + 84196
5 libjvm.dylib 0x26c2440d 0x26c10000 + 82957
6 libjvm.dylib 0x26c24297 0x26c10000 + 82583
7 libjvm.dylib 0x26d4f365 0x26c10000 + 1307493
8 libjvm.dylib 0x26d4f2d3 0x26c10000 + 1307347
9 libjvm.dylib 0x26c42535 0x26c10000 + 206133
10 libjvm.dylib 0x26c2436c 0x26c10000 + 82796
11 libsystem_c.dylib 0x936bf5b7 _pthread_start + 344
12 libsystem_c.dylib 0x936a9d4e thread_start + 34
Thread 23:: Java: VM Thread
0 libsystem_kernel.dylib 0x97b697d2 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x97b68cb0 mach_msg + 68
2 libjvm.dylib 0x26c24b96 0x26c10000 + 84886
3 libjvm.dylib 0x26c4271a 0x26c10000 + 206618
4 libjvm.dylib 0x26c248e4 0x26c10000 + 84196
5 libjvm.dylib 0x26c2440d 0x26c10000 + 82957
6 libjvm.dylib 0x26c24297 0x26c10000 + 82583
7 libjvm.dylib 0x26cbd402 0x26c10000 + 709634
8 libjvm.dylib 0x26cbd0ab 0x26c10000 + 708779
9 libjvm.dylib 0x26c2436c 0x26c10000 + 82796
10 libsystem_c.dylib 0x936bf5b7 _pthread_start + 344
11 libsystem_c.dylib 0x936a9d4e thread_start + 34
Thread 24:: Java: Reference Handler
0 libsystem_kernel.dylib 0x97b697d2 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x97b68cb0 mach_msg + 68
2 libjvm.dylib 0x26c24ac6 0x26c10000 + 84678
3 libjvm.dylib 0x26c24a02 0x26c10000 + 84482
4 libjvm.dylib 0x26ccc56c 0x26c10000 + 771436
5 libjvm.dylib 0x26ccba6e 0x26c10000 + 768622
6 libjvm.dylib 0x26ccb75d JVM_MonitorWait + 211
7 libjvmlinkage.dylib 0x18063dd5 JVM_MonitorWait + 69
8 ??? 0x2f52b9d9 0 + 793950681
9 ??? 0x2f523e31 0 + 793919025
10 ??? 0x2f523e31 0 + 793919025
11 ??? 0x2f521374 0 + 793908084
12 libjvm.dylib 0x26cbe76f 0x26c10000 + 714607
13 libjvm.dylib 0x26cbe4e1 0x26c10000 + 713953
14 libjvm.dylib 0x26ccb405 0x26c10000 + 766981
15 libjvm.dylib 0x26ccb28d 0x26c10000 + 766605
16 libjvm.dylib 0x26ccb20c 0x26c10000 + 766476
17 libjvm.dylib 0x26ccb059 0x26c10000 + 766041
18 libjvm.dylib 0x26ccae8f 0x26c10000 + 765583
19 libjvm.dylib 0x26c2436c 0x26c10000 + 82796
20 libsystem_c.dylib 0x936bf5b7 _pthread_start + 344
21 libsystem_c.dylib 0x936a9d4e thread_start + 34
Thread 25:: Java: Finalizer
0 libsystem_kernel.dylib 0x97b697d2 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x97b68cb0 mach_msg + 68
2 libjvm.dylib 0x26c24ac6 0x26c10000 + 84678
3 libjvm.dylib 0x26c24a02 0x26c10000 + 84482
4 libjvm.dylib 0x26ccc56c 0x26c10000 + 771436
5 libjvm.dylib 0x26ccba6e 0x26c10000 + 768622
6 libjvm.dylib 0x26ccb75d JVM_MonitorWait + 211
7 libjvmlinkage.dylib 0x18063dd5 JVM_MonitorWait + 69
8 ??? 0x2f52b9d9 0 + 793950681
9 ??? 0x2f523e31 0 + 793919025
10 ??? 0x2f523f97 0 + 793919383
11 ??? 0x2f523f97 0 + 793919383
12 ??? 0x2f521374 0 + 793908084
13 libjvm.dylib 0x26cbe76f 0x26c10000 + 714607
14 libjvm.dylib 0x26cbe4e1 0x26c10000 + 713953
15 libjvm.dylib 0x26ccb405 0x26c10000 + 766981
16 libjvm.dylib 0x26ccb28d 0x26c10000 + 766605
17 libjvm.dylib 0x26ccb20c 0x26c10000 + 766476
18 libjvm.dylib 0x26ccb059 0x26c10000 + 766041
19 libjvm.dylib 0x26ccae8f 0x26c10000 + 765583
20 libjvm.dylib 0x26c2436c 0x26c10000 + 82796
21 libsystem_c.dylib 0x936bf5b7 _pthread_start + 344
22 libsystem_c.dylib 0x936a9d4e thread_start + 34
Thread 26:: Java: Surrogate Locker Thread (Concurrent GC)
0 libsystem_kernel.dylib 0x97b697d2 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x97b68cb0 mach_msg + 68
2 libjvm.dylib 0x26c24ac6 0x26c10000 + 84678
3 libjvm.dylib 0x26c24a02 0x26c10000 + 84482
4 libjvm.dylib 0x26c248c8 0x26c10000 + 84168
5 libjvm.dylib 0x26c2440d 0x26c10000 + 82957
6 libjvm.dylib 0x26c241da 0x26c10000 + 82394
7 libjvm.dylib 0x26cdc884 0x26c10000 + 837764
8 libjvm.dylib 0x26cdc7c8 0x26c10000 + 837576
9 libjvm.dylib 0x26ccb059 0x26c10000 + 766041
10 libjvm.dylib 0x26ccae8f 0x26c10000 + 765583
11 libjvm.dylib 0x26c2436c 0x26c10000 + 82796
12 libsystem_c.dylib 0x936bf5b7 _pthread_start + 344
13 libsystem_c.dylib 0x936a9d4e thread_start + 34
Thread 27:: Java: Signal Dispatcher
0 libsystem_kernel.dylib 0x97b6980e semaphore_wait_trap + 10
1 libjvm.dylib 0x26cdd172 0x26c10000 + 840050
2 libjvm.dylib 0x26cdcb48 0x26c10000 + 838472
3 libjvm.dylib 0x26ccb059 0x26c10000 + 766041
4 libjvm.dylib 0x26ccae8f 0x26c10000 + 765583
5 libjvm.dylib 0x26c2436c 0x26c10000 + 82796
6 libsystem_c.dylib 0x936bf5b7 _pthread_start + 344
7 libsystem_c.dylib 0x936a9d4e thread_start + 34
Thread 28:: Java: C1 CompilerThread0
0 libsystem_kernel.dylib 0x97b697d2 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x97b68cb0 mach_msg + 68
2 libjvm.dylib 0x26c24ac6 0x26c10000 + 84678
3 libjvm.dylib 0x26c24a02 0x26c10000 + 84482
4 libjvm.dylib 0x26c248c8 0x26c10000 + 84168
5 libjvm.dylib 0x26c2440d 0x26c10000 + 82957
6 libjvm.dylib 0x26c241da 0x26c10000 + 82394
7 libjvm.dylib 0x26ce4c06 0x26c10000 + 871430
8 libjvm.dylib 0x26cde358 0x26c10000 + 844632
9 libjvm.dylib 0x26cde102 0x26c10000 + 844034
10 libjvm.dylib 0x26ccb059 0x26c10000 + 766041
11 libjvm.dylib 0x26ccae8f 0x26c10000 + 765583
12 libjvm.dylib 0x26c2436c 0x26c10000 + 82796
13 libsystem_c.dylib 0x936bf5b7 _pthread_start + 344
14 libsystem_c.dylib 0x936a9d4e thread_start + 34
Thread 29:: Java: Low Memory Detector
0 libsystem_kernel.dylib 0x97b697d2 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x97b68cb0 mach_msg + 68
2 libjvm.dylib 0x26c24ac6 0x26c10000 + 84678
3 libjvm.dylib 0x26c24a02 0x26c10000 + 84482
4 libjvm.dylib 0x26c248c8 0x26c10000 + 84168
5 libjvm.dylib 0x26c2440d 0x26c10000 + 82957
6 libjvm.dylib 0x26c24297 0x26c10000 + 82583
7 libjvm.dylib 0x26cdf098 0x26c10000 + 848024
8 libjvm.dylib 0x26ccb059 0x26c10000 + 766041
9 libjvm.dylib 0x26ccae8f 0x26c10000 + 765583
10 libjvm.dylib 0x26c2436c 0x26c10000 + 82796
11 libsystem_c.dylib 0x936bf5b7 _pthread_start + 344
12 libsystem_c.dylib 0x936a9d4e thread_start + 34
Thread 30:: Java: VM Periodic Task Thread
0 libsystem_kernel.dylib 0x97b697d2 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x97b68cb0 mach_msg + 68
2 libjvm.dylib 0x26c24b96 0x26c10000 + 84886
3 libjvm.dylib 0x26c4271a 0x26c10000 + 206618
4 libjvm.dylib 0x26ce1c49 0x26c10000 + 859209
5 libjvm.dylib 0x26c2436c 0x26c10000 + 82796
6 libsystem_c.dylib 0x936bf5b7 _pthread_start + 344
7 libsystem_c.dylib 0x936a9d4e thread_start + 34
Thread 31:: Java: FelixDispatchQueue
0 libsystem_kernel.dylib 0x97b697d2 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x97b68cb0 mach_msg + 68
2 libjvm.dylib 0x26c24ac6 0x26c10000 + 84678
3 libjvm.dylib 0x26c24a02 0x26c10000 + 84482
4 libjvm.dylib 0x26ccc56c 0x26c10000 + 771436
5 libjvm.dylib 0x26ccba6e 0x26c10000 + 768622
6 libjvm.dylib 0x26ccb75d JVM_MonitorWait + 211
7 libjvmlinkage.dylib 0x18063dd5 JVM_MonitorWait + 69
8 ??? 0x2f52b9d9 0 + 793950681
9 ??? 0x2f523e31 0 + 793919025
10 ??? 0x2f523e31 0 + 793919025
11 ??? 0x2f523e31 0 + 793919025
12 ??? 0x2f523e31 0 + 793919025
13 ??? 0x2f52430d 0 + 793920269
14 ??? 0x2f521374 0 + 793908084
15 libjvm.dylib 0x26cbe76f 0x26c10000 + 714607
16 libjvm.dylib 0x26cbe4e1 0x26c10000 + 713953
17 libjvm.dylib 0x26ccb405 0x26c10000 + 766981
18 libjvm.dylib 0x26ccb28d 0x26c10000 + 766605
19 libjvm.dylib 0x26ccb20c 0x26c10000 + 766476
20 libjvm.dylib 0x26ccb059 0x26c10000 + 766041
21 libjvm.dylib 0x26ccae8f 0x26c10000 + 765583
22 libjvm.dylib 0x26c2436c 0x26c10000 + 82796
23 libsystem_c.dylib 0x936bf5b7 _pthread_start + 344
24 libsystem_c.dylib 0x936a9d4e thread_start + 34
Thread 32:: Java: FelixStartLevel
0 libsystem_kernel.dylib 0x97b697d2 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x97b68cb0 mach_msg + 68
2 libjvm.dylib 0x26c24ac6 0x26c10000 + 84678
3 libjvm.dylib 0x26c24a02 0x26c10000 + 84482
4 libjvm.dylib 0x26ccc56c 0x26c10000 + 771436
5 libjvm.dylib 0x26ccba6e 0x26c10000 + 768622
6 libjvm.dylib 0x26ccb75d JVM_MonitorWait + 211
7 libjvmlinkage.dylib 0x18063dd5 JVM_MonitorWait + 69
8 ??? 0x2f52b9d9 0 + 793950681
9 ??? 0x2f523e31 0 + 793919025
10 ??? 0x2f523e31 0 + 793919025
11 ??? 0x2f52430d 0 + 793920269
12 ??? 0x2f521374 0 + 793908084
13 libjvm.dylib 0x26cbe76f 0x26c10000 + 714607
14 libjvm.dylib 0x26cbe4e1 0x26c10000 + 713953
15 libjvm.dylib 0x26ccb405 0x26c10000 + 766981
16 libjvm.dylib 0x26ccb28d 0x26c10000 + 766605
17 libjvm.dylib 0x26ccb20c 0x26c10000 + 766476
18 libjvm.dylib 0x26ccb059 0x26c10000 + 766041
19 libjvm.dylib 0x26ccae8f 0x26c10000 + 765583
20 libjvm.dylib 0x26c2436c 0x26c10000 + 82796
21 libsystem_c.dylib 0x936bf5b7 _pthread_start + 344
22 libsystem_c.dylib 0x936a9d4e thread_start + 34
Thread 33:: Java: FelixPackageAdmin
0 libsystem_kernel.dylib 0x97b697d2 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x97b68cb0 mach_msg + 68
2 libjvm.dylib 0x26c24ac6 0x26c10000 + 84678
3 libjvm.dylib 0x26c24a02 0x26c10000 + 84482
4 libjvm.dylib 0x26ccc56c 0x26c10000 + 771436
5 libjvm.dylib 0x26ccba6e 0x26c10000 + 768622
6 libjvm.dylib 0x26ccb75d JVM_MonitorWait + 211
7 libjvmlinkage.dylib 0x18063dd5 JVM_MonitorWait + 69
8 ??? 0x2f52b9d9 0 + 793950681
9 ??? 0x2f523e31 0 + 793919025
10 ??? 0x2f523e31 0 + 793919025
11 ??? 0x2f52430d 0 + 793920269
12 ??? 0x2f521374 0 + 793908084
13 libjvm.dylib 0x26cbe76f 0x26c10000 + 714607
14 libjvm.dylib 0x26cbe4e1 0x26c10000 + 713953
15 libjvm.dylib 0x26ccb405 0x26c10000 + 766981
16 libjvm.dylib 0x26ccb28d 0x26c10000 + 766605
17 libjvm.dylib 0x26ccb20c 0x26c10000 + 766476
18 libjvm.dylib 0x26ccb059 0x26c10000 + 766041
19 libjvm.dylib 0x26ccae8f 0x26c10000 + 765583
20 libjvm.dylib 0x26c2436c 0x26c10000 + 82796
21 libsystem_c.dylib 0x936bf5b7 _pthread_start + 344
22 libsystem_c.dylib 0x936a9d4e thread_start + 34
Thread 34:: Java: Thread-4
0 libsystem_kernel.dylib 0x97b697d2 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x97b68cb0 mach_msg + 68
2 libjvm.dylib 0x26c24b96 0x26c10000 + 84886
3 libjvm.dylib 0x26d5a18d 0x26c10000 + 1352077
4 libjvm.dylib 0x26d5d6c6 JVM_Sleep + 254
5 libjvmlinkage.dylib 0x180649c8 JVM_Sleep + 72
6 ??? 0x2f52b9d9 0 + 793950681
7 ??? 0x2f523e31 0 + 793919025
8 ??? 0x2f52430d 0 + 793920269
9 ??? 0x2f521374 0 + 793908084
10 libjvm.dylib 0x26cbe76f 0x26c10000 + 714607
11 libjvm.dylib 0x26cbe4e1 0x26c10000 + 713953
12 libjvm.dylib 0x26ccb405 0x26c10000 + 766981
13 libjvm.dylib 0x26ccb28d 0x26c10000 + 766605
14 libjvm.dylib 0x26ccb20c 0x26c10000 + 766476
15 libjvm.dylib 0x26ccb059 0x26c10000 + 766041
16 libjvm.dylib 0x26ccae8f 0x26c10000 + 765583
17 libjvm.dylib 0x26c2436c 0x26c10000 + 82796
18 libsystem_c.dylib 0x936bf5b7 _pthread_start + 344
19 libsystem_c.dylib 0x936a9d4e thread_start + 34
Thread 35:
0 libsystem_kernel.dylib 0x97b6bc72 __semwait_signal + 10
1 libsystem_c.dylib 0x93749a55 nanosleep$UNIX2003 + 189
2 com.adobe.flash.flbridge 0x1d63f93b ScObjects::Thread::sleep(unsigned int) + 59
3 com.adobe.flash.flbridge 0x1d63b799 ScObjects::BridgeTalkThread::run() + 185
4 com.adobe.flash.flbridge 0x1d63fca8 ScObjects::Thread::go(void*) + 168
5 libsystem_c.dylib 0x936bf5b7 _pthread_start + 344
6 libsystem_c.dylib 0x936a9d4e thread_start + 34Hi Sangeeta,
I am not sure how to provide the sample file which is crashing?
Repro Steps:
1. I would create a motion tween
2. Make an end point on the timeline for the objects position
3. Retrace through each point on the timeline to make a path for the object to follow to reach the end point.
4. At each frame on the timeline which I was altering the shape, a black dot would appear.
5. I would use the Free Transform tool by right clicking on the object.
6. I would rotate/scale the object or Option+Click on a anchor point on the shape to just move that one point and not the entire shape.
7. Program would crash immediately after letting go of the mouse.
Maybe you are looking for
-
Only one DVI works on the dock
I just purchased two new Dell U2412M displays (1920x1200) for use with my W530 and dock. I had planned to plug them both into the DVI ports on the dock, but it seems like this is problematic. When I do so, I only get an image out of the display on po
-
Insufficient privilege when run SQL in PL/SQL Developer
Hi, My developer had strange behavior when run below SQL from PL/SQL Developer. It will come out with "*Insufficient Privileges*" message. SELECT Fiscal FROM pmaps_fiscalweekonly WHERE intend >= trunc(sysdate) AND rownum < 5 ORDER BY intend ASC; Same
-
Setting the doc.type to use for t.code ABUMN (transfer asset ...)
Hi All, Could anyone show me where to set, in customizing, the doc.type to use for t.code ABUMN (transfer asset within company code)? Thanks Umberto Gandalf
-
Contents of DynamicUtilTreeNode
Hello, The code snippet below is part of an effort to create a tree of JTextFields. When I run the program, I do indeed see my tree hierarchy. But instead of the intended text fields, I see instead the string representation of these text field fields
-
Financial Document results not OK
Hi All, I have one issue that when user enters the Financial documentno in the sales order its giving the error. Financial document is for LC ( Letter of credit ) Financial Document:Check::Deadlines Check result : Not OK Message NO E1574 Diagnosis: A