Hi Laurent
I have never used VS2013, I upgraded directly form 2012.

My best guess is that something is being deleted twice, by removing
that line of code it may be that some things are not deleted at all,
so you may end up with memory leaks.

As I mentioned before, the destructor was modified after the commit
you last checked out, which may have fixed the problem. The next check
should be to check out the latest version of PLPlot to see if that
helps.

You are correct that VS2015 seems to be quite different and is binary
incompatible with previous versions. I had a number of problems when I
upgraded too.

Phil

On 13 January 2016 at 09:33, Laurent Berger
<laurent.ber...@univ-lemans.fr> wrote:
> Hi,
>
> I need to resume before further insvestigations
> on my computer
> VS2013 wx3.1.0(commit 25-nov 2015)  plplot (commit 22 dec 2015) ==> no
> problem
> VS2015 wx3.1.0(commit 25-nov 2015)  plplot (commit 22 dec 2015) ==> bug in
> closing window
>
> on your computer
> VS2013 wx3.0.2  plplot (commit 22 dec 2015)  ==> no problem
> VS2015 wx3.0.2   plplot (commit 22 dec 2015)  ==> no problem
>
> I think VS 2015 compiler is not like vs2013 compiler
>
> I have comment line 2527 of plcore.c : plPTidy() and there is no exception.
> Of course it is not an answer to this problem but i think it helps to
> localize this problem.
>
> As you are not able to reproduce my error  may be something is wrong in my
> configuration. I can stay with VS 2013
>
> Laurent
>
>
>
>
> Le 11/01/2016 18:54, Phil Rosenberg a écrit :
>>
>> Hi Laurent
>> I am unfortunately so far unable to reproduce your error. I have tried
>> checking out the same commit that you have and still I do not see the
>> same error
>>
>> I can only think that this must be something to do with the new
>> version of wxWidgets. I will try to look into it further, but I am not
>> sure exactly when I will be able to upgrade to that version. Hopefully
>> later this week.
>>
>> However, later on the 22nd Dec - the same day you checked out your
>> version of PLPlot, I changed the destructor of wxPLplotwindow to
>> virtual, which it should have been all the time, because wxWidgets is
>> probably deleting it via a wxWindow * pointer. There is a chance this
>> may have fixed your issue. Can you please check out the latest version
>> of from the git repo and let me know if you still have the same
>> problem.
>>
>> If the problem persists can I just confirm that you are getting the
>> second stack trace twice identically? If you are then that is very
>> strange as it means that  plend() is getting called twice somehow.
>>
>> Also it is worth noting that I have just made some commits that fix
>> some not quite correct aspect ratio problems that the wxWidgets driver
>> was having (although I'm not sure if they existed when you pass a wxDC
>> in, maybe just when run from non-wxWidgets apps).
>>
>> Phil
>>
>> On 9 January 2016 at 09:11, Phil Rosenberg <p.d.rosenb...@gmail.com>
>> wrote:
>>>
>>> Hi Laurent
>>> I am working with wxWidgets 3.0.2. Perhaps there have been some changes.
>>>
>>> However, looking at your two stack traces I think there is a plplot
>>> problem.
>>> It looks like the wxPlplotwindow destructor is being called twice, once
>>> by
>>> plplot and once by wxWidgets.
>>>
>>> I will look at this today and get back to you asap.
>>>
>>> Phil
>>> ________________________________
>>> From: Laurent Berger
>>> Sent: ‎08/‎01/‎2016 21:35
>>> To: Phil Rosenberg
>>> Subject: Re: [Plplot-devel] Uisng plplot with wxwidgets and vs 2015
>>>
>>> Hi phil
>>>
>>> i use git from git://git.code.sf.net/p/plplot/plplot
>>> Using git log I have got this :
>>> commit b90635d9fcba816f5bdd75c547c18bfe25d67ec0
>>> Author: Phil Rosenberg <p.d.rosenb...@gmail.com>
>>> Date:   Tue Dec 22 11:52:17 2015 +0000
>>> I'm working too with windows 10
>>>
>>> my wxWidgets is 3.1.0 with last commit from 8 jan 2016
>>>
>>> Le 08/01/2016 22:24, Phil Rosenberg a écrit :
>>>
>>> Hi Laurent
>>> Are you using the latest development version or the latest release
>>> version?
>>>
>>> I have also just swapped to VS2015 and the current development version I
>>> working for me on Windows 10.
>>> ________________________________
>>> From: Laurent Berger
>>> Sent: ‎08/‎01/‎2016 20:23
>>> To: plplot-devel@lists.sourceforge.net
>>> Subject: [Plplot-devel]  Uisng plplot with wxwidgets and vs 2015
>>>
>>> Hi,
>>>
>>> I want to use VS2015 now with wxwidgets and plplot. When I wxPlplotDemo
>>> It works fine until I press close box. An exception occurs at line 273
>>> wxWidgets-3.1.0/src/common/dcgraph.cpp stack. When I set a breakpoint at
>>> line 273 in dcgraph.cpp stack trace for first call
>>>>
>>>>     wxPLplotDemo.exe!wxGCDCImpl::~wxGCDCImpl() Ligne 273    C++
>>>
>>>        [Code externe]
>>>        wxPLplotDemo.exe!wxDC::~wxDC() Ligne 742    C++
>>>        wxPLplotDemo.exe!wxGCDC::~wxGCDC() Ligne 122    C++
>>>        [Code externe]
>>> wxPLplotDemo.exe!wxPLplotwindow<wxFrame>::~wxPLplotwindow<wxFrame>()
>>> Ligne 110    C++
>>>        [Code externe]
>>>        wxPLplotDemo.exe!wxAppConsoleBase::DeletePendingObjects() Ligne
>>> 637    C++
>>>        wxPLplotDemo.exe!wxAppConsoleBase::ProcessIdle() Ligne 445 C++
>>>        wxPLplotDemo.exe!wxAppBase::ProcessIdle() Ligne 373    C++
>>>        wxPLplotDemo.exe!wxEventLoopBase::ProcessIdle() Ligne 98    C++
>>>        wxPLplotDemo.exe!wxEventLoopManual::DoRun() Ligne 263    C++
>>>        wxPLplotDemo.exe!wxEventLoopBase::Run() Ligne 76    C++
>>>        wxPLplotDemo.exe!wxAppConsoleBase::MainLoop() Ligne 380    C++
>>>        wxPLplotDemo.exe!wxAppConsoleBase::OnRun() Ligne 302    C++
>>>        wxPLplotDemo.exe!wxAppBase::OnRun() Ligne 312    C++
>>>        wxPLplotDemo.exe!wxEntryReal(int & argc, wchar_t * * argv) Ligne
>>> 503    C++
>>>        wxPLplotDemo.exe!wxEntry(int & argc, wchar_t * * argv) Ligne
>>> 181    C++
>>>        wxPLplotDemo.exe!wxEntry(HINSTANCE__ * hInstance, HINSTANCE__ *
>>> __formal, char * __formal, int nCmdShow) Ligne 290    C++
>>>        wxPLplotDemo.exe!WinMain(HINSTANCE__ * hInstance, HINSTANCE__ *
>>> hPrevInstance, char * __formal, int nCmdShow) Ligne 129    C++
>>>        [Code externe]
>>>
>>> If i go on debugging I reach break point twice with this statck trace
>>>
>>>>     wxPLplotDemo.exe!wxGCDCImpl::~wxGCDCImpl() Ligne 273    C++
>>>
>>>        [Code externe]
>>>        wxPLplotDemo.exe!wxDC::~wxDC() Ligne 742    C++
>>>        wxPLplotDemo.exe!wxGCDC::~wxGCDC() Ligne 122    C++
>>>        [Code externe]
>>>        wxPLplotDemo.exe!wxPLDevice::~wxPLDevice() Ligne 543    C++
>>>        [Code externe]
>>>        wxPLplotDemo.exe!plD_tidy_wxwidgets(PLStream * pls) Ligne 383
>>> C++
>>>        wxPLplotDemo.exe!plP_tidy() Ligne 235    C
>>>        wxPLplotDemo.exe!c_plend1() Ligne 2528    C
>>>        wxPLplotDemo.exe!plstream::~plstream() Ligne 347    C++
>>>        wxPLplotDemo.exe!wxPLplotstream::~wxPLplotstream() Ligne 91 C++
>>> wxPLplotDemo.exe!wxPLplotwindow<wxFrame>::~wxPLplotwindow<wxFrame>()
>>> Ligne 111    C++
>>>        [Code externe]
>>>        wxPLplotDemo.exe!wxAppConsoleBase::DeletePendingObjects() Ligne
>>> 637    C++
>>>        wxPLplotDemo.exe!wxAppConsoleBase::ProcessIdle() Ligne 445 C++
>>>        wxPLplotDemo.exe!wxAppBase::ProcessIdle() Ligne 373    C++
>>>        wxPLplotDemo.exe!wxEventLoopBase::ProcessIdle() Ligne 98    C++
>>>        wxPLplotDemo.exe!wxEventLoopManual::DoRun() Ligne 263    C++
>>>        wxPLplotDemo.exe!wxEventLoopBase::Run() Ligne 76    C++
>>>        wxPLplotDemo.exe!wxAppConsoleBase::MainLoop() Ligne 380    C++
>>>        wxPLplotDemo.exe!wxAppConsoleBase::OnRun() Ligne 302    C++
>>>        wxPLplotDemo.exe!wxAppBase::OnRun() Ligne 312    C++
>>>        wxPLplotDemo.exe!wxEntryReal(int & argc, wchar_t * * argv) Ligne
>>> 503    C++
>>>        wxPLplotDemo.exe!wxEntry(int & argc, wchar_t * * argv) Ligne
>>> 181    C++
>>>        wxPLplotDemo.exe!wxEntry(HINSTANCE__ * hInstance, HINSTANCE__ *
>>> __formal, char * __formal, int nCmdShow) Ligne 290    C++
>>>        wxPLplotDemo.exe!WinMain(HINSTANCE__ * hInstance, HINSTANCE__ *
>>> hPrevInstance, char * __formal, int nCmdShow) Ligne 129    C++
>>>        [Code externe]
>>>
>>> An if press step exception occurs this->m_graphicContexthas been
>>> 0xFFFFFFFFFFF7...
>>>
>>> With VS 2013 there is no problem and setting breakpoint at same point
>>> this breakpoint is reach only once.
>>> I have build plplot with static lib and shared  lib  using release or
>>> debug mode and that's change nothing.
>>>
>>> Have you got an idea to help me solving  this problem?
>>>
>>> Thanks in advance
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Site24x7 APM Insight: Get Deep Visibility into Application Performance
>>> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
>>> Monitor end-to-end web transactions and take corrective actions now
>>> Troubleshoot faster and improve end-user experience. Signup Now!
>>> http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
>>> _______________________________________________
>>> Plplot-devel mailing list
>>> Plplot-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/plplot-devel
>>>
>>>
>

------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
_______________________________________________
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel

Reply via email to