|
|
|
|||||
|
Crash on exit, after upgrade to Ice 3.2
I just upgraded from Ice 3.1.1 to Ice 3.2.1. After the upgrade, one of my servers crashes whenever I try to shut it down. The shutdown is through icegridadmin (server stop <server name>).
Here's the crash stack: Quote:
Quote:
<Edit - added valgrind output> For kicks I ran valgrind on the executable. The output is full of 'Invalid read of size 8' and 'Address is 24 bytes inside a block of size 48 free'd'. I've attached two of the pertinent reports, all caused on application exit. Last edited by vanco : 04-04-2008 at 09:47 PM. Reason: Attaching valgrind output |
|
|||||
|
Didn't work...
Sorry - changing boost::shared_ptr to IceUtil::Handle and deriving MyImpl from IceUtil::Shared didn't work. That makes sense - since both just do reference counting.
I'll try to cook up a simple example that replicates my problem. In the meantime, any suggestions are welcome. |
|
|||||
|
One more hint
Forgot to mention this: the crash on exit only happens once at least one of the servants have been invoked at least once. When I stop the server immediately after it starts up, without executing any of its functions, I see no crash on exit.
|
|
|||||
|
no luck reproducing on a small testcase
No luck reproducing the problem on a small testcase - the small testcase works like a charm.
Instead, I tried going top-down - started removing code from my server, until it started working. Interestingly, it started working when I removed some completely innocuous line of code (a=b*c, where all three are floating points). It almost looks like either an uninitialized variable, or a race condition, most likely in the guts of Ice (since valgrind cannot find it in my code). Building the debug version of Ice to see if that will show anything... |
|
|||||
|
bug was in user code
Managed to track the bug to user code. There was a bug in the destruction sequence of the MyImpl object.
Curiously, though - this bug was never triggered in 3.1.1. It's almost like the MyImpl object was never destroyed in 3.1.1... If it were destroyed, this bug would have shown up immediately. |
![]() |
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Upgrade to ice 3.2 : problem with Icegrid admin session | Vivien Delage | Help Center | 2 | 10-15-2007 05:13 AM |
| ICE in COM DLL Server can not exit?? | jans | Help Center | 2 | 07-17-2007 04:19 AM |
| Patch #1 for Ice 3.2: fix for IceGrid registry assert/crash | benoit | Patches | 0 | 04-20-2007 07:11 AM |
| v3.1.1 upgrade issue | dthompson | Help Center | 1 | 12-19-2006 01:53 PM |
| Java VM Crash within Ice.CommunicatorI.destroy and many threads w/ Prioxies. | jae | Help Center | 3 | 10-17-2006 10:09 PM |