#3204 closed defect (fixed)
wxExecute hangs on intel based Mac
Reported by: | eilers | Owned by: | csomor |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | old wxOSX/Carbon port | Version: | |
Keywords: | OSX | Cc: | eilers, csomor, al@… |
Blocked By: | Blocking: | ||
Patch: | no |
Description
There is a real problem with intel based Mac's and the wxExecute
command.
(tested and reproduced with the current CVS version, compiled on a
MacBook Pro!)
If it used with wxEXEC_SYNC, it just hangs in the following while loop:
int wxGUIAppTraits::WaitForChild(wxExecuteData& execData)
{
[...]
while ( endProcData->pid != 0 )
{
[...]
}
[...]
}
It seems as if nobody is setting the pid to 0..
If it is used with wxEXEC_ASYNC like this:
wxExecute(command,wxEXEC_ASYNC,theMakeProcess);
The method "OnTerminate()" is never called.
It looks as if the internal process notifcations are failing!
Btw.: It does not matter whether I disable one processor of my dualcore
system!!
Change History (5)
comment:1 Changed 10 years ago by wxsite
- Status changed from assigned to confirmed
comment:2 Changed 10 years ago by alarsen
- Cc al@… added
- Keywords OSX added
Is this bug still present in 2.9-svn on current OSX?
Cheers
Anders
comment:3 Changed 5 years ago by oneeyeman
Tried to test this with exec sample on the latest TRUNK Cocoa build.
Running something either synchronously or a-synchronously does not produce a hanging.
However there is another problem:
- Run the sample.
- Go to "exec->Quit exec". Nothing happens.
Clicking on the red "X" closes the application.
comment:4 Changed 5 years ago by vadz
- Resolution set to fixed
- Status changed from confirmed to closed
transitioning old 'assigned' status to new 'confirmed' status